Techniques for indicating a dynamic subframe type

ABSTRACT

Techniques are described for wireless communication. One method includes identifying a traffic condition associated with data to be transmitted between a network access device and at least one user equipment (UE); selecting, based at least in part on the traffic condition, a dynamic subframe type of a time-division duplex (TDD) subframe; and indicating the dynamic subframe type in a TDD header of the TDD subframe. Another method includes identifying, in a TDD header of a subframe, an indication of a dynamic subframe type of the TDD subframe; and transmitting data or receiving data in a data region of the TDD subframe based at least in part on the dynamic subframe type.

CROSS REFERENCES

The present Application for Patent claims priority to U.S. ProvisionalPatent Application No. 62/267,903 by Ang et al., entitled “Techniquesfor Dynamically Indicating a Time-Division Duplex (TDD) Subframe Type,”filed Dec. 15, 2015 and U.S. Provisional Patent Application No.62/377,466 by Ang et al., entitled “Techniques for DynamicallyIndicating a Time-Division Duplex (TDD) Subframe Type,” filed Aug. 19,2016, assigned to the assignee hereof, and hereby expressly incorporatedby reference herein in their entirety.

INTRODUCTION

The present disclosure, for example, relates to wireless communicationsystems, and more particularly to techniques for dynamically indicatinga dynamic subframe type.

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower). Examples of such multiple-access systems include code-divisionmultiple access (CDMA) systems, time-division multiple access (TDMA)systems, frequency-division multiple access (FDMA) systems, andorthogonal frequency-division multiple access (OFDMA) systems.

In some examples, a wireless multiple-access communication system mayinclude a number of base stations, each simultaneously supportingcommunication for multiple communication devices, otherwise known asuser equipment (UEs). In a Long-Term Evolution (LTE) or LTE-Advanced(LTE-A) network, a set of one or more base stations may define an eNodeB(eNB). In other examples (e.g., in a next generation or 5G network), awireless multiple access communication system may include a number ofsmart radio heads (RHs) in communication with a number of access nodecontrollers (ANCs), where a set of one or more RHs, in communicationwith an ANC, defines an eNB. A base station or RH may communicate with aset of UEs on downlink (DL) channels (e.g., for transmissions from abase station or RH to a UE) and uplink (UL) channels (e.g., fortransmissions from a UE to a base station or RH).

Subframes of communication between a network access device (e.g., aneNB, an ANC, a RH, or a base station) and a plurality of UEs may includedifferent regions or channels that are assembled in accordance with atime division duplex (TDD) and/or frequency division duplex (FDD)subframe structure. Subframes may also include arrangements of ULchannels and/or DL channels. In LTE/LTE-A networks, the datatransmission direction of a subframe (e.g., UL and/or DL) ispre-determined or fixed.

SUMMARY

A method of wireless communication is described. The method may includeselecting a dynamic subframe type of a TDD subframe and indicating thedynamic subframe type in a TDD header of the TDD subframe.

An apparatus for wireless communication is described. The apparatus mayinclude means for selecting a dynamic subframe type of a TDD subframeand means for indicating the dynamic subframe type in a TDD header ofthe TDD subframe.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to select a dynamic subframe type ofa TDD subframe and indicate the dynamic subframe type in a TDD header ofthe TDD subframe.

A non-transitory computer readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to select a dynamic subframetype of a TDD subframe and indicate the dynamic subframe type in a TDDheader of the TDD subframe.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe indicated within a temporally first symbol period of the TDDsubframe.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for transmitting a downlink controlregion of the TDD header within at least one of: the temporally firstsymbol period of the TDD subframe, or the temporally first symbol periodof the TDD subframe and a temporally second symbol period of the TDDsubframe.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe selected from a set of dynamic subframe types including two or moreof: a downlink-centric dynamic subframe type, or an uplink-centricdynamic subframe type, or a bi-directional dynamic subframe type, or afull-duplex dynamic subframe type, or a dynamic switch dynamic subframetype, or a mixed interference measurement dynamic subframe type, or adistributed scheduling dynamic subframe type.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for at least one of: allocating ahybrid automatic repeat request (HARQ) transmission period for the TDDsubframe at an end of the TDD subframe, or allocating at least one HARQtransmission resource for the TDD subframe in a downlink control regionof a subsequent subframe, or allocating at least one downlink HARQtransmission resource for the TDD subframe and at least one uplink HARQtransmission resource for the TDD subframe in the TDD subframe.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for at least one of: broadcasting thedynamic subframe type to UEs associated with a cell, or unicasting thedynamic subframe type to a subset of UEs associated with the cell. Someexamples of the method, apparatus, and non-transitory computer-readablemedium described above may further include processes, features, means,or instructions for scheduling a data region of the TDD subframe basedat least in part on the selected dynamic subframe type.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for indicating the dynamic subframetype in a downlink control region of the TDD subframe. Some examples ofthe method, apparatus, and non-transitory computer-readable mediumdescribed above may further include processes, features, means, orinstructions for scheduling a guard period between the downlink controlregion and the data region when the dynamic subframe type may beassociated with a data region having an uplink portion.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, indicating the dynamicsubframe type comprises: transmitting an indication of the dynamicsubframe type within a narrow band of frequencies of a system bandwidth.In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, indicating the dynamicsubframe type comprises: transmitting at least one of: a first bitindicating an uplink data transmission direction or a downlink datatransmission direction, or a second bit indicating a half-duplex datatransmission or a full-duplex data transmission, or a combinationthereof.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for indicating the dynamic subframetype comprises at least one of: embedding an indication of the dynamicsubframe type in a reference signal, or transmitting the indication ofthe dynamic subframe type in a subframe type indicator channel, ortransmitting a type of downlink control information (DCI) correspondingto the dynamic subframe type.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for identifying a traffic conditionassociated with data to be transmitted between a network access deviceand at least one UE, the traffic condition comprising an uplink/downlinktraffic ratio.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe selected based at least in part on the traffic condition. In someexamples of the method, apparatus, and non-transitory computer-readablemedium described above, the uplink/downlink traffic ratio comprises aratio of traffic queued for transmission to the network access deviceand traffic queued for transmission to the at least one UE.

A method of wireless communication is described. The method may includeidentifying, in a TDD header of a TDD subframe, an indication of adynamic subframe type of the TDD subframe and transmitting data orreceiving data in a data region of the TDD subframe based at least inpart on the dynamic subframe type.

An apparatus for wireless communication is described. The apparatus mayinclude means for identifying, in a TDD header of a TDD subframe, anindication of a dynamic subframe type of the TDD subframe and means fortransmitting data or receiving data in a data region of the TDD subframebased at least in part on the dynamic subframe type.

Another apparatus for wireless communication is described. The apparatusmay include a processor, memory in electronic communication with theprocessor, and instructions stored in the memory. The instructions maybe operable to cause the processor to identify, in a TDD header of a TDDsubframe, an indication of a dynamic subframe type of the TDD subframeand transmit data or receiving data in a data region of the TDD subframebased at least in part on the dynamic subframe type.

A non-transitory computer readable medium for wireless communication isdescribed. The non-transitory computer-readable medium may includeinstructions operable to cause a processor to identify, in a TDD headerof a TDD subframe, an indication of a dynamic subframe type of the TDDsubframe and transmit data or receiving data in a data region of the TDDsubframe based at least in part on the dynamic subframe type.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe identified within a temporally first symbol period of the TDDsubframe. Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for receiving a downlink control regionof the TDD header within at least one of: the temporally first symbolperiod of the TDD subframe, or the temporally first symbol period of theTDD subframe and a temporally second symbol period of the TDD subframe.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe typecomprises: a downlink-centric dynamic subframe type, or anuplink-centric dynamic subframe type, or a bi-directional dynamicsubframe type, or a full-duplex dynamic subframe type, or a dynamicswitch dynamic subframe type, or a mixed interference measurementdynamic subframe type, or a distributed scheduling dynamic subframetype.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for identifying at least one of: anallocation of a HARQ transmission period for the TDD subframe at an endof the TDD subframe, or an allocation of at least one HARQ transmissionresource for the TDD subframe in a downlink control region of asubsequent subframe, or an allocation of at least one downlink HARQtransmission resource for the TDD subframe and at least one uplink HARQtransmission resource for the TDD subframe in the TDD subframe.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe received in at least one of: broadcast control information, orunicast control information. Some examples of the method, apparatus, andnon-transitory computer-readable medium described above may furtherinclude processes, features, means, or instructions for identifying thedynamic subframe type in a downlink control region of the TDD subframe.Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, or instructions for refraining from transmitting duringa guard period between the downlink control region and the data regionwhen the dynamic subframe type may be associated with a data regionhaving an uplink portion.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, identifying the dynamicsubframe type comprises: identifying an indication of the dynamicsubframe type within a narrow band of frequencies of a system bandwidth.In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, wherein identifying thedynamic subframe type comprises: receiving at least one of: a first bitindicating an uplink data transmission direction or a downlink datatransmission direction, or a second bit indicating a half-duplex datatransmission or a full-duplex data transmission, or a combinationthereof.

In some examples of the method, apparatus, and non-transitorycomputer-readable medium described above, the dynamic subframe type maybe identified based at least in part on at least one of: an indicationof the dynamic subframe type embedded in a reference signal, or anindication of the dynamic subframe type received in a subframe typeindicator channel, or a type of received DCI.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentdisclosure may be realized by reference to the following drawings. Inthe appended figures, similar components or functions may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 illustrates an example of a wireless communication system, inaccordance with one or more aspects of the disclosure;

FIG. 2A shows an example of a subframe associated with a DL-centricdynamic subframe type, in accordance with one or more aspects of thepresent disclosure;

FIG. 2B shows an example of a subframe associated with a UL-centricdynamic subframe type, in accordance with one or more aspects of thepresent disclosure;

FIG. 2C shows an example of a subframe associated with a bi-directionaldynamic subframe type, in accordance with one or more aspects of thepresent disclosure;

FIG. 3 illustrates an example of a first subframe associated with aDL-centric dynamic subframe type, and a second subframe associated witha UL-centric dynamic subframe type, in accordance with one or moreaspects of the present disclosure;

FIGS. 4A, 4B, and 4C show examples of subframes associated with adynamic switch dynamic subframe type, in accordance with one or moreaspects of the present disclosure;

FIGS. 5A and 5B show examples of subframes associated with a mixedinterference measurement dynamic subframe type, in accordance with oneor more aspects of the present disclosure;

FIG. 6 shows an example of a subframe associated with a distributedscheduling dynamic subframe type, in accordance with one or more aspectsof the present disclosure;

FIG. 7 is a flow chart illustrating an example of a method forindicating a dynamic subframe type in a subframe type indicator channel,in accordance with one or more aspects of the present disclosure;

FIG. 8A shows an example timeline of operations performed by a networkaccess device for a subframe associated with a DL-centric dynamicsubframe type, in accordance with one or more aspects of the presentdisclosure;

FIG. 8B shows an example timeline of operations performed by a networkaccess device for a subframe associated with a UL-centric dynamicsubframe type, in accordance with one or more aspects of the presentdisclosure;

FIG. 9A shows an example timeline of operations performed by a UE for asubframe associated with a DL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure;

FIG. 9B shows an example timeline of operations performed by a UE for asubframe associated with a UL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure;

FIG. 10 illustrates an example of resources and UE process timing for asubframe associated with a DL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure;

FIG. 11 illustrates an example of resources and UE process timing for asubframe associated with a UL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure;

FIG. 12 illustrates an example of resources and UE process timing for asubframe associated with a UL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure;

FIG. 13 shows a block diagram of an apparatus for use in wirelesscommunication, in accordance with one or more aspects of the presentdisclosure;

FIG. 14 shows a block diagram of a wireless communication manager foruse in wireless communication, in accordance with one or more aspects ofthe present disclosure;

FIG. 15 shows a block diagram of an apparatus for use in wirelesscommunication, in accordance with one or more aspects of the presentdisclosure;

FIG. 16 shows a block diagram of a wireless communication manager foruse in wireless communication, in accordance with one or more aspects ofthe present disclosure;

FIG. 17 shows a block diagram of a network access device for use inwireless communication, in accordance with one or more aspects of thepresent disclosure;

FIG. 18 shows a block diagram of a UE for use in wireless communication,in accordance with one or more aspects of the present disclosure;

FIG. 19 is a flow chart illustrating an example of a method for wirelesscommunication, in accordance with one or more aspects of the presentdisclosure;

FIG. 20 is a flow chart illustrating an example of a method for wirelesscommunication, in accordance with one or more aspects of the presentdisclosure;

FIG. 21 is a flow chart illustrating an example of a method for wirelesscommunication, in accordance with one or more aspects of the presentdisclosure; and

FIG. 22 is a flow chart illustrating an example of a method for wirelesscommunication, in accordance with one or more aspects of the presentdisclosure.

DETAILED DESCRIPTION

Techniques are described in which dynamic subframe types are indicatedfor a TDD subframe. Next generation networks (e.g., 5G networks) arebeing designed to support features such as high bandwidth operations,more dynamic subframe types, and self-contained subframe types (in whichHARQ feedback for a subframe may be transmitted before the end of thesubframe). Techniques for structuring subframes for LTE/LTE-Acommunications may not be adequate for next generation (or 5G) networks.For example, the high and frequently changing traffic loads that a 5Gnetwork is expected to serve may not be efficiently serviced by apre-determined or fixed subframe structure. Thus, support for dynamicselection and indication of a subframe type may be necessary to supporthigh and frequently changing traffic loads.

A network access device (e.g., an eNB, an ANC, an RH, or a base station)may identify a traffic condition (e.g., a UL/DL traffic ratio)associated with data to be transmitted between the network access deviceand at least one UE. The UL/DL traffic ratio may be a ratio of trafficqueued for transmission to the network access device and traffic queuedfor transmission to the at least one UE. Based at least in part on thetraffic condition, a dynamic subframe type may be selected for anupcoming (e.g., next) subframe. The selected dynamic subframe type may,for example, be selected from a set of dynamic subframe types, such asdownlink-centric, uplink-centric, bi-directional, full-duplex, dynamicswitch, mixed interference measurement, and distributed schedulingdynamic subframe types. The selected dynamic subframe type may beindicated to one or more UEs in a TDD header of a TDD subframe. In thismanner, the TDD subframe for which the dynamic subframe type is selectedmay be self-contained (e.g., all control information pertaining to theTDD subframe, including HARQ feedback for the TDD subframe, may betransmitted within the TDD subframe).

In some cases, to support multiplexing of different classes of users andrequirements, some attributes of a subframe may change dynamically. Asan example, subframe numerology, which defines the tone spacing, cyclicprefix duration, symbol duration, a number of transmission timeintervals (TTIs) within a subframe, a number of symbols per TTI, thepresence of a common UL burst and associated attributes, a duration of aguard period, a frequency domain partition of the subframe (i.e.,subbanding), etc., may dynamically change in a wireless communicationssystem. Additionally or alternatively, subframes with differentattributes may be classified as different dynamic subframe types and bedynamically selected for use.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various operations may be added, omitted, orcombined. Additionally or alternatively, features described with respectto some examples may be combined in some other examples.

FIG. 1 illustrates an example of a wireless communication system 100, inaccordance with one or more aspects of the disclosure. The wirelesscommunication system 100 may include network access devices 105, UEs115, and a core network 130. The core network 130 may provide userauthentication, access authorization, tracking, Internet Protocol (IP)connectivity, and other access, routing, or mobility functions. At leastsome of the network access devices 105 (e.g., eNBs 105-a or ANCs 105-b)may interface with the core network 130 through backhaul links 132(e.g., S1, S2, etc.) and may perform radio configuration and schedulingfor communication with the UEs 115. In various examples, the ANCs 105-bmay communicate, either directly or indirectly (e.g., through corenetwork 130), with each other over backhaul links 134 (e.g., X1, X2,etc.), which may be wired or wireless communication links. Each ANC105-b may also communicate with a number of UEs 115 through a number ofsmart RHs 105-c. In an alternative configuration of the wirelesscommunication system 100, the functionality of an ANC 105-b may beprovided by a RH 105-c or distributed across the RHs 105-c of an eNB105-a. In another alternative configuration of the wirelesscommunication system 100, the RHs 105-c may be replaced with basestations, and the ANCs 105—may be replaced by base station controllers(or links to the core network 130).

A macro cell may cover a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs 115 withservice subscriptions with a network provider. A small cell may includea lower-powered RH or base station, as compared with a macro cell, andmay operate in the same or different frequency band(s) as macro cells.Small cells may include pico cells, femto cells, and micro cellsaccording to various examples. A pico cell may cover a relativelysmaller geographic area and may allow unrestricted access by UEs 115with service subscriptions with a network provider. A femto cell alsomay cover a relatively small geographic area (e.g., a home) and mayprovide restricted access by UEs 115 having an association with thefemto cell (e.g., UEs in a closed subscriber group (CSG), UEs for usersin the home, and the like). An eNB for a macro cell may be referred toas a macro eNB. An eNB for a small cell may be referred to as a smallcell eNB, a pico eNB, a femto eNB or a home eNB. An eNB may support oneor multiple (e.g., two, three, four, and the like) cells (e.g.,component carriers).

The wireless communication system 100 may support synchronous orasynchronous operation. For synchronous operation, the eNBs 105-a and/orRHs 105-c may have similar frame timing, and transmissions fromdifferent eNBs 105-a and/or RHs 105-c may be approximately aligned intime. For asynchronous operation, the eNBs 105-a and/or RHs 105-c mayhave different frame timings, and transmissions from different eNBs105-a and/or RHs 105-c may not be aligned in time. The techniquesdescribed herein may be used for either synchronous or asynchronousoperations.

The communication networks that may accommodate some of the variousdisclosed examples may be packet-based networks that operate accordingto a layered protocol stack. In the user plane, communications at thebearer or packet data convergence protocol (PDCP) layer may be IP-based.A radio link control (RLC) layer may in some cases perform packetsegmentation and reassembly to communicate over logical channels. Amedium access control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use HARQ to provide retransmission at the MAC layer to improvelink efficiency. In the control plane, the radio resource control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 115 and a RH 105-c, ANC 105-b, or corenetwork 130 supporting radio bearers for user plane data. At thephysical (PHY) layer, transport channels may be mapped to physicalchannels.

The UEs 115 may be dispersed throughout the wireless communicationsystem 100, and each UE 115 may be stationary or mobile. A UE 115 mayalso include or be referred to by those skilled in the art as a mobilestation, a subscriber station, a mobile unit, a subscriber unit, awireless unit, a remote unit, a mobile device, a wireless device, awireless communications device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology. A UE 115 may be a cellular phone, apersonal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a tablet computer, a laptopcomputer, a cordless phone, a wireless local loop (WLL) station, anInternet of Everything (IoE) device, or the like. A UE may be able tocommunicate with various types of eNBs 105-a, RHs 105-c, base stations,access points, or other network access devices, including macro eNBs,small cell eNBs, relay base stations, and the like. A UE may also beable to communicate directly with other UEs (e.g., using a peer-to-peer(P2P) protocol).

The communication links 125 shown in wireless communication system 100may include UL channels from a UE 115 to a RH 105-c, and/or DL channels,from a RH 105-c to a UE 115. The DL channels may also be called forwardlink channels, while the UL channels may also be called reverse linkchannels. Control information and data may be multiplexed on a ULchannel or DL channel according to various techniques. Controlinformation and data may be multiplexed on a DL channel, for example,using time-division multiplexing (TDM) techniques (e.g., as describedwith reference to FIG. 2 ), frequency-division multiplexing (FDM)techniques (e.g., as described with reference to FIG. 3 ), or hybridTDM-FDM techniques (e.g., as described with reference to FIG. 7, 8 , or9). In some examples, the control information transmitted during a TTIof a DL channel may be distributed between different control regions ina cascaded manner (e.g., between a common control region and one or moreUE-specific control regions).

One or more of the network access devices 105 (e.g., one or more eNBs105-a) may include a network access device wireless communicationmanager 1320. In some examples, the network access device wirelesscommunication manager 1320 may be an example of the wirelesscommunication manager 1320 described with reference to FIG. 13, 14 , or17, and may be used to identify a traffic condition associated with datato be transmitted between a network access device and at least one UE115. The network access device wireless communication manager 1320 mayalso be used to select, based at least in part on the traffic condition,a dynamic subframe type of a subframe, and to indicate the dynamicsubframe type in a TDD header of the TDD subframe.

One or more of the UEs 115 may include a UE wireless communicationmanager 1520. In some examples, the UE wireless communication manager1520 may be an example of the wireless communication manager 1520described with reference to FIG. 15, 16 , or 18, and may be used toidentify, in a TDD header of a subframe, an indication of a dynamicsubframe type of the TDD subframe. The UE wireless communication manager1520 may also be used to transmit data or receive data in a data regionof the TDD subframe based at least in part on the dynamic subframe type.

Each communication link 125 may include one or more carriers, where eachcarrier may be a signal made up of multiple sub-carriers (e.g., waveformsignals of different frequencies) modulated according to one or moreradio access technologies. Each modulated signal may be sent on adifferent sub-carrier and may carry control information (e.g., referencesignals, control channels, etc.), overhead information, user data, etc.The communication links 125 may transmit bidirectional communicationsusing FDD techniques (e.g., using paired spectrum resources) or TDDtechniques (e.g., using unpaired spectrum resources). Frame structuresfor FDD (e.g., frame structure type 1) and TDD (e.g., frame structuretype 2) may be defined.

In some examples of the wireless communication system 100, the RHs 105-cand/or UEs 115 may include multiple antennas for employing antennadiversity schemes to improve communication quality and reliabilitybetween RHs 105-c and UEs 115. Additionally or alternatively, RHs 105-cand/or UEs 115 may employ multiple-input, multiple-output (MIMO)techniques that may take advantage of multi-path environments totransmit multiple spatial layers carrying the same or different codeddata.

The wireless communication system 100 may support operation on multiplecells or carriers, a feature which may be referred to as carrieraggregation (CA) or multi-carrier operation. A carrier may also bereferred to as a component carrier (CC), a layer, a channel, etc. Theterms “carrier,” “component carrier,” “cell,” and “channel” may be usedinterchangeably herein. A UE 115 may be configured with multiple DL CCsand one or more UL CCs CA. CA may be used with both FDD and TDD CCs.

FIGS. 2A, 2B, and 2C show various examples of dynamic subframe types.The dynamic subframe types illustrated in FIGS. 2A, 2B, and 2C may beexamples of subframe types selected for a TDD subframe. FIG. 2A shows anexample of a subframe 200 associated with a DL-centric dynamic subframetype, in accordance with one or more aspects of the present disclosure.In some examples, the DL-centric dynamic subframe type may be selectedfor the subframe 200, by a network access device, based at least in parton a UL/DL traffic ratio. For example, the network access device mayselect a DL-centric dynamic subframe type for the subframe 200 when theUL/DL traffic ratio that indicates more traffic is queued by the networkaccess device for transmission to one or more UEs than is queued by theone or more UEs for transmission to the network access device.Alternatively, and by way of further example, the network access devicemay select a DL-centric dynamic subframe type for the subframe 200 whenthe UL/DL ratio indicates a particular percentage of the total amount oftraffic queued for one or more UEs is DL traffic, or when a particularpercentage of the DL traffic included in the UL/DL ratio is associatedwith a priority above a threshold. In some examples, the network accessdevice and UEs that communicate in the subframe 200 may be examples ofaspects of the network access devices 105 and UEs 115 described withreference to FIG. 1 .

The subframe 200 may begin with a header 205 including a DL controlregion. An indication of the DL-centric dynamic subframe type of thesubframe 200 may be transmitted to one or more UEs that transmit orreceive data during the subframe 200, by the network access device, inthe header 205 (and/or in the DL control region). Following the header205, the network access device may schedule a data region 210 of thesubframe 200 (e.g., a DL data region). Following the data region 210,the network access device may schedule a UL control region 215 and/orallocate at least one HARQ transmission resource for a UE (or UEs) totransmit HARQ feedback for the subframe 200 (e.g., one or more positiveacknowledgments (ACKs) or negative acknowledgments (NACKs)) to thenetwork access device. The UL control region 215 and/or at least oneHARQ transmission resource may be optionally bounded by a first guardperiod 220 and a second guard period 225 in the time domain, to give UEstime to perform RF switching. In some examples, the subframe 200 mayhave a self-contained subframe structure (e.g., a subframe structure inwhich all transmissions during the subframe are ACK'd or NAK'd duringthe subframe).

FIG. 2B shows an example of a subframe 230 associated with a UL-centricdynamic subframe type, in accordance with one or more aspects of thepresent disclosure. In some examples, the UL-centric dynamic subframetype may be selected for the subframe 230, by a network access device,based at least in part on a UL/DL traffic ratio. For example, thenetwork access device may select a UL-centric dynamic subframe type forthe subframe 230 when the UL/DL traffic ratio indicates more traffic isqueued by one or more UEs for transmission to the network access devicethan is queued by the network access device for transmission to the oneor more UEs. Alternatively, and by way of further example, the networkaccess device may select a UL-centric dynamic subframe type for thesubframe 230 when the UL/DL ratio indicates a particular percentage ofthe total amount of queued traffic for one or more UEs may be ULtraffic, or when a particular percentage of the UL traffic included inthe UL/DL ratio may be associated with a priority above a threshold. Insome examples, the network access device and UEs that communicate in thesubframe 230 may be examples of aspects of the network access devices105 and UEs 115 described with reference to FIG. 1 .

The subframe 230 may begin with a header 235 including a DL controlregion. An indication of the UL-centric dynamic subframe type of thesubframe 230 may be transmitted to one or more UEs that transmit orreceive data in the subframe 230, by the network access device, in theheader 235 (and/or in the DL control region). Following the header 235,the network access device may schedule a data region 240 of the subframe230 (e.g., a UL data region). The data region 240 may be optionallyseparated from the header 235 by a first guard period 245 in the timedomain, to give UEs time to perform RF switching.

Following the data region 240, the network access device may optionallyschedule a DL control region 250 and/or allocate at least one HARQtransmission resource for the network access device to transmit HARQfeedback for the subframe 230 (e.g., one or more ACKs or NAKs) to one ormore UEs. The DL control region 250 and/or at least one HARQtransmission resource may be optionally bounded by a second guard period255 in the time domain, to give UEs time to perform RF switching.Alternatively, the DL control region 250 may not be provided, and may bemerged into a DL control region of a subsequently-transmitted subframe.In some examples, the subframe 230 may have a self-contained subframestructure (e.g., a subframe structure in which all transmissions duringthe subframe are ACK'd or NAK'd during the subframe).

FIG. 2C shows an example of a subframe 265 associated with abi-directional dynamic subframe type, in accordance with one or moreaspects of the present disclosure. In some examples, the bi-directionaldynamic subframe type may be selected for the subframe 265, by a networkaccess device, based at least in part on a UL/DL traffic ratio. Forexample, the network access device may select a bi-directional dynamicsubframe type for the subframe 265 when the UL/DL traffic ratioindicates traffic is queued by one or more UEs for transmission to thenetwork access device and traffic is queued by the network access devicefor transmission to the one or more UEs. Alternatively, and by way offurther example, the network access device may select a bi-directionaldynamic subframe type for the subframe 265 when a particular percentageof both the UL traffic and the DL traffic included in the UL/DL ratio isassociated with a priority above a threshold. In some examples, thenetwork access device and UEs that communicate in the subframe 265 maybe examples of aspects of the network access devices 105 and UEs 115described with reference to FIG. 1 .

A subframe 265 may begin with a header 270 including a DL controlregion. An indication of the bi-directional dynamic subframe type of thesubframe 265 may be transmitted to one or more UEs that may transmit orreceive data in the subframe 265, by the network access device, in theheader 270 (and/or in the DL control region). Following the header 270,the network access device may schedule a UL control region 275, which isfollowed by a plurality of data regions of the subframe 265 (e.g., afirst data region 280 (e.g., a DL data region), and a second data region285 (e.g., a UL data region)). The UL control region 275 may beoptionally separated from the header 270 by a first guard period 290 inthe time domain, to give UEs 115 time to perform RF switching.Similarly, the second data region 285 may be optionally separated fromthe first data region 280 by a second guard period 295. In someexamples, the second data region 285 may be part of a UL regionincluding another UL control region and/or an allocation of at least oneHARQ transmission resource for a UE 115 (or UEs 115) to transmit HARQfeedback for the subframe 265 (e.g., one or more ACKs or NAKs) to thenetwork access device; Alternatively, the UL control information couldalso be deferred to the UL control region of a subsequently-transmitted,rendering the subframe structure non-self-contained.

Following the second data region 285, the network access device mayoptionally schedule a downlink control region 297 and/or allocate atleast one HARQ transmission resource for the network access device totransmit HARQ feedback for the subframe 265 (e.g., one or more ACKs orNAKs) to one or more UEs. Alternatively, the DL control region 297 maynot be included in subframe 265, and may be merged into a DL controlregion of a subsequently-transmitted subframe. In some examples, thesubframe 265 may have a self-contained subframe structure (e.g., asubframe structure in which all transmissions during the subframe areACK'd or NAK'd during the subframe).

Some subframes (e.g., some subframes other than those shown in FIGS. 2A,2B, and 2C) may be associated with other dynamic subframe types, such asa full-duplex dynamic subframe type (not shown). The headers 205, 235,and 270 of the subframes 200, 230, and 265 described with reference toFIGS. 2A, 2B, and 2C may have a same or similar structure, with eachheader including an indication of a dynamic subframe type. In someexamples, a dynamic subframe type may be identified before the dataregion(s) of a corresponding subframe are decoded or transmitted. Insome examples, a dynamic subframe type associated with a subframe may betransmitted to a UE in a temporally first symbol period of a two (ormore) symbol period DL control region. In this manner, a UE may completeidentification (e.g., decoding) of the dynamic subframe type during asecond or subsequent symbol period of the DL control region (i.e.,before receipt of a data region of the subframe). In the case of asubframe having a UL data region following the subframe's header, a UEmay complete identification (e.g., decoding) of a dynamic subframe typeassociated with the subframe during a guard period following the header.

In some examples, a dynamic subframe type may be indicated bybroadcasting the dynamic subframe type to UEs associated with a networkaccess device (or cell). In some examples, a dynamic subframe type maybe indicated by unicasting the dynamic subframe type to a subset of UEsassociated with a network access device (or cell). In some examples, thesubset of UEs to which a dynamic subframe type is unicast may include asubset of UEs that are active during the subframe for which the dynamicsubframe type is unicast (e.g., a subset of non-discontinuous reception(non-DRX) mode UEs). Unicast transmission of a dynamic subframe type maybe useful, for example, if a wireless communication system or networkaccess device allows a multiplexing (or simultaneous transmission) ofdifferent dynamic subframe types, or when a number of UEs only supportunicast control. In some examples, a dynamic subframe type may beindicated by transmitting an indication of the dynamic subframe typewithin a narrow band of frequencies of a system bandwidth, as describedwith reference to FIG. 3 .

In some examples, a dynamic subframe type may be indicated bytransmitting an indicator (or set of indicators) that distinguishbetween a DL-centric dynamic subframe type and a UL-centric dynamicsubframe type, or between a DL-centric dynamic subframe type, aUL-centric dynamic subframe type, a full-duplex dynamic subframe type, adynamic switch dynamic subframe type, a mixed interference measurementdynamic subframe type, or a distributed scheduling dynamic subframetype. In some cases, the dynamic subframe type may be determined using acombination of the content of the indication (i.e., one or more bits)and any context or mode that has been configured. That is, a number ofbits used for the indication may be content dependent. For example, awireless communications system may be configured to support a subset ofdynamic subframe types, and this subset of dynamic subframe types maynot change dynamically. As a result, the indication may only need tospecify which dynamic subframe type(s) within the subset of dynamicsubframe types is in use for a TDD subframe. In another example, a UEmay have previously used a subset of dynamic subframe types, and basedon the subset of previously used dynamic subframe types, the UE maydetermine how to interpret the bits used for the indication of thedynamic subframe type. Accordingly, additional information associatedwith identifying various dynamic subframe types may be kept relativelysmall.

In some examples, a dynamic subframe type may be indicated bytransmitting at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction and/or asecond bit indicating a half-duplex data transmission or a full-duplexdata transmission. In some examples, UEs that are not capable ofcommunicating according to a full-duplex subframe structure may ignorethe second bit and communicate in accordance with the first bit, or mayignore the subframe when the second bit indicates a full-duplex dynamicsubframe type.

FIG. 3 illustrates an example 300 of a first subframe 305 associatedwith a DL-centric dynamic subframe type, and a second subframe 310associated with a UL-centric dynamic subframe type, in accordance withone or more aspects of the present disclosure. In some examples, thenetwork access device and UEs that communicate in the first subframe 305or the second subframe 310 may be examples of aspects of the networkaccess devices 105 and UEs 115 described with reference to FIG. 1 .

As mentioned above, some subframes may have a self-contained subframestructure. In the example of FIG. 3 , the subframe 305 includes a DLportion 315 and a UL portion 320. The UL portion 320 may be bounded oneither side, in the time domain, by guard periods. A DL control region325 may be transmitted at a beginning of the DL portion 315, within asubset of frequency resources of the DL portion 315, and over one or twosymbol periods of the DL portion 315. The DL control region 325 mayinclude an indication of a dynamic subframe type (e.g., a DL-centricdynamic subframe type) for the subframe 305. In some examples, the DLcontrol region 325 may include a subset of frequency resources that havea narrower bandwidth than the total bandwidth used for communicationbetween the network access device and a UE.

The relatively narrow bandwidth of the DL control region 325 may allowfor reduced reference signal (e.g., cell-specific reference signal(CRS)) overhead relative to a wider bandwidth, and may allow forlower-tier UEs (e.g., machine-type communication (MTC) UEs) to access anetwork through a network access device with reduced hardware complexityand reduced power consumption. In some examples, the resources of the DLcontrol region 325 may be multiplexed in frequency, within the symbolsused to transmit the DL control region 325, with resources allocated toa DL data region 330. Frequency multiplexing of the DL control region325 may enable utilization of more or all of the channel bandwidthduring the symbol periods used to transmit the DL control region 325,despite the DL control region 325 only occupying a narrow band of thetotal bandwidth used for communication between the network access deviceand a UE. The subframe 305 may end, in some examples, with a ULtransmission 335, which may be referred to as a “UL common burst” whenits structure is shared by subframes associated with a TDD DL-centricsubframe type and subframes associated with a TDD UL-centric subframetype. Scheduling of the UL transmission 335 may be independent of the DLdata region 330, or may be pre-scheduled, in some examples.

In the subframe 310, a DL portion 340 is located at the beginning of thesubframe 310, followed by a guard period 355 during which RF circuitrymay be switched from receive mode to transmit mode, followed by a ULportion 360. A second guard period 370 may follow the UL portion 360 toprovide for switching of transmit/receive circuitry from the transmitmode back to the receive mode in preparation for reception of a DLcontrol region of a subsequent subframe. Within the DL portion 340, a DLcontrol region 350 may occupy a portion of the entire transmissionbandwidth, similarly to the DL control region 325 of the subframe 305.

The DL control region 350 may include an indication of a dynamicsubframe type (e.g., a UL-centric dynamic subframe type) for thesubframe 310. The DL control region 350 may be multiplexed with other DLdata resources 345 in order to utilize the entire transmissionbandwidth. The UL portion 360 may include a UL data region 365. The ULportion 360 may also include a UL common burst 335, which may beformatted similarly to the UL common burst described with reference tothe subframe 305. Thus, both the DL-centric subframe 305 and theUL-centric subframe 310 may have self-contained TDD subframe structures.

A dynamic subframe type may be indicated in various ways. For example,an indication of a dynamic subframe type may be embedded in a referencesignal, such as CRS. When embedded in a reference signal, in someexamples, hypothesis testing may be used to determine the value of onebit of information indicating a DL-centric dynamic subframe type or aUL-centric dynamic subframe type. As another example, an indication of adynamic subframe type may be transmitted in a subframe type indicatorchannel, as described, for example, with reference to FIG. 7 . As yetanother example, a dynamic subframe type may be indicated bytransmitting a type of DCI corresponding to the dynamic subframe type.For example, a DL assignment may be transmitted in a subframe associatedwith a DL-centric dynamic subframe type, and a UL grant may betransmitted in a subframe associated with a UL-centric dynamic subframetype. In some examples, other types of DCI may be transmitted for asubframe associated with a bi-directional dynamic subframe type or afull-duplex dynamic subframe type.

FIGS. 4A, 4B, and 4C show examples of dynamic subframe types used fordynamic frame switching. In some cases, a wireless communications systemmay support dynamic scheduling of mixed UL and DL transmissions, and mayuse UL or DL-centric dynamic subframes that include additional featuresused in dynamic frame switching environments, such as channel clearingfeatures (e.g., clear-to-send (CTS) messages) and override messages. Thedynamic subframe types illustrated in FIGS. 4A, 4B, and 4C may beexamples of dynamic subframe types selected for a TDD subframe. FIG. 4Ashows an example of subframe 400 associated with a dynamic switchdynamic subframe type, in accordance with one or more aspects of thepresent disclosure. In some cases, a dynamic switch dynamic subframetype may be selected for subframe 400, by a network access device, suchas a base station, based at least in part on a traffic condition, suchas a UL/DL traffic ratio. In some examples, the network access deviceand UEs that communicate in subframe 400 may be examples of aspects ofthe network access devices 105 and UEs 115 described with reference toFIG. 1 .

Subframe 400 may begin with a DL/UL scheduling information region 405,where an indication of the dynamic switch dynamic subframe type ofsubframe 400 may be transmitted, by the network access device to one ormore UEs that may transmit or receive data in subframe 400, in DL/ULscheduling information region 405, in a control region, or in some otherregion. In some cases, DL/UL scheduling information may be transmittedin a control channel (e.g., a physical downlink control channel(PDCCH)), and may be transmitted to a UE in a temporally first symbolperiod of a two (or more) symbol period control region.

Following the DL/UL scheduling information region 405, the networkaccess device may schedule a DL/UL CTS region 415. The DL/UL CTS regionmay include a CTS message used to clear a channel, such as a channel inunlicensed RF spectrum, from communication by neighboring devices (e.g.,neighboring UEs and network access devices). As a result, the CTSmessage may silence surrounding devices and any interference that may becaused by those devices. The DL/UL CTS region 415 may be bounded by afirst guard period 410 and a second guard period 420. A DL/UL dataregion 425 of subframe 400 may then be scheduled by the network accessdevice, and a UL control region 430 may follow the DL/UL data region 425of subframe 400. In some examples, subframe 400 may have aself-contained dynamic switch dynamic subframe structure (e.g., asubframe structure in which all transmissions during the subframe areACK'd or NACK'd during the subframe).

FIG. 4B shows an example of subframe 435 associated with a dynamicswitch dynamic subframe type, in accordance with one or more aspects ofthe present disclosure. A dynamic switch dynamic subframe type may beselected for subframe 435, by a network access device, based at least inpart on a traffic condition. In some examples, the network access deviceand UEs that communicate in subframe 435 may be examples of aspects ofthe network access devices 105 and UEs 115 described with reference toFIG. 1 . Subframe 435 may begin with a DL/UL scheduling informationregion 440. As described above, an indication of the dynamic switchdynamic subframe type of subframe 435 may be transmitted using DL/ULscheduling information region 440, a control region, or in some otherregion. In some examples, the indication of the dynamic switch dynamicsubframe type may be included in a temporally first symbol period of atwo (or more) symbol period control region of subframe 435. In thismanner, a UE may complete identification (e.g., decoding) of the dynamicswitch dynamic subframe type during a second or subsequent symbol periodof the DL control region (i.e., before receipt of a data region of thesubframe).

Following the DL/UL scheduling information region 440, the networkaccess device may schedule a DL/UL data region 450, where DL/UL dataregion 450 may be separated from DL/UL scheduling information region 440by a guard period 445. UL control region 455 used for the transmissionof UL control information by a UE may be included in subframe 435following the DL/UL data region 450.

FIG. 4C shows an example of a subframe 460 associated with a dynamicswitch dynamic subframe type, in accordance with one or more aspects ofthe present disclosure. A dynamic switch dynamic subframe type may beselected for subframe 460, by a network access device, based at least inpart on a traffic condition. In some examples, the network access deviceand UEs that communicate in subframe 460 may be examples of aspects ofthe network access devices 105 and UEs 115 described with reference toFIG. 1 . Subframe 460 may begin with a DL/UL scheduling informationregion 465, which may include an indication of the dynamic subframe typein a temporally first symbol period.

Subframe 460 may include, following a DL/UL scheduling informationregion 465, a DL/UL override region 475. The DL/UL override region 475may include an override message that provides an indication of resourcesassociated with DL or UL communications. In some examples, DL/ULoverride region 475 may be optionally bounded by a first guard period470 and a second guard period 480. The network access device may furtherschedule a DL/UL data region 485 followed by a UL control region 490 insubframe 460.

A dynamic switch dynamic subframe type may be indicated in various ways.For example, an indication of a dynamic switch dynamic subframe type maybe embedded in a reference signal. As another example, an indication ofa dynamic switch dynamic subframe type may be transmitted in a subframetype indicator channel, as described, for example, with reference toFIG. 7 . In another example, a dynamic switch dynamic subframe type maybe indicated by transmitting a type of DCI corresponding to the dynamicswitch dynamic subframe type.

FIGS. 5A and 5B show various examples of dynamic subframe types that maybe used for updating jamming graphs based on mixed interferencemeasurements. In some cases, a wireless communications system maysupport mixed UL and DL transmissions, which may be network scheduled bya network access device based at least in part on jamming graphs (e.g.,semi-statically updated jamming graphs that summarize UL/DL and DL/ULmixed interference). Accordingly, the network access device may schedulemixed interference measurement dynamic subframe types. The dynamicsubframe types illustrated in FIGS. 5A and 5B may be examples of dynamicsubframe types selected for a TDD subframe. FIG. 5A shows an example ofsubframes 500 associated with a mixed interference measurement dynamicsubframe type, in accordance with one or more aspects of the presentdisclosure. In some cases, a mixed interference dynamic subframe typemay be selected for subframes 500, by a network access device such as abase station, based at least in part on a traffic condition (e.g., aUL/DL traffic ratio). Subframes 500 may illustrate an example ofUL-centric dynamic subframe types scheduled for respective UEs (e.g.,subframes 505-a, 505-b and 505-c for a first, second, and third UErespectively). In some examples, the network access device and UEs thatcommunicate using subframes 500 may be examples of aspects of thenetwork access devices 105 and UEs 115 described with reference to FIG.1 .

Each of the subframes 500 may begin with a DL control region 510, whichmay include an indication, to multiple UEs that may transmit or receivedata in subframes 505-a, 505-b, and 505-c, of the mixed interferencemeasurement dynamic subframe type of subframes 500. In some examples,the mixed interference measurement dynamic subframe type may beidentified before the other regions of a corresponding subframe aredecoded or transmitted. For example, a mixed interference measurementdynamic subframe type associated with subframes 500 may be transmittedto a UE in a temporally first symbol period of a two (or more) symbolperiod DL control region. In this manner, a UE may completeidentification (e.g., decoding) of the mixed interference measurementdynamic subframe type during a second or subsequent symbol period of theDL control region (i.e., before receipt of a data region of thesubframe).

Following the DL control region 510, the network access device mayschedule a measurement region 520 in each of the subframes 500, wherethe measurement region 520, in some examples, is separated from DLcontrol region 510 by a guard period 515. Measurement region 520 may beused by a UE to transmit during a subset of SRS regions, and performsignal measurements (e.g., from the other UEs using subframes 500)during the SRS regions in which the UE is not transmitting. For example,a first UE may transmit SRS in a first subset of SRS regions of firstsubframe 505-a (e.g., SRS regions 525 transmitted in SRS regions 1 and2), and may listen for the remaining duration of the measurement region520 (e.g., SRS regions 3 through 6). Using second subframe 505-b, asecond UE may perform measurements of the SRS transmitted by the firstUE (during SRS regions 525) and transmit SRS in a second subset of SRSregions (e.g., SRS regions 530 transmitted in SRS regions 3 and 4) andsubsequently perform measurements for the remainder of measurementregion 520. Additional UEs scheduled to use the mixed interferencemeasurement dynamic subframe type may perform similar operations duringa different subset of SRS regions (e.g., a third UE may performmeasurements in subframe 505-c while the first and second UEs transmitSRS, and subsequently transmit SRS during SRS region 535). The networkaccess device may then schedule a UL control region 540 in each of thesubframes 500. In some examples, subframes 500 may have a self-containedmixed interference measurement dynamic subframe structure (e.g., asubframe structure in which all transmissions during the subframe areACK'd or NACK'd during the subframe).

FIG. 5B shows an example of subframes 550 associated with a mixedinterference measurement dynamic subframe type, in accordance with oneor more aspects of the present disclosure. In some cases, a mixedinterference dynamic subframe type may be selected for subframes 550, bya network access device such as a base station, based at least in parton a UL/DL traffic ratio. Subframes 550 may illustrate an example ofUL-centric dynamic subframe types scheduled for respective UEs (e.g.,subframes 555-a, 555-b and 555-c for a first, second, and third UErespectively), where the UEs may be scheduled to transmit simultaneously(e.g., using different frequency resources). In some examples, thenetwork access device and UEs that communicate using subframes 550 maybe examples of aspects of the network access devices 105 and UEs 115described with reference to FIG. 1 .

Each of the subframes 550 may begin with a DL control region 560, whichmay include an indication, to multiple UEs that may transmit or receivedata in subframes 555-a, 555-b, and 555-c, of the mixed interferencemeasurement dynamic subframe type of subframe 550. For example, a mixedinterference measurement dynamic subframe type associated with subframes550 may be transmitted to UEs in a temporally first symbol period of atwo (or more) symbol period DL control region. Following the DL controlregion 560, the network access device may schedule a measurement region570 in each of the subframes 550. Measurement region 570 may be used bya UE to transmit during a subset of SRS regions, which may correspond tosubband partitioning of the subframe, and perform signal measurements(e.g., from the other UEs using subframes 550) during the SRS regions inwhich the UE is not transmitting.

In some cases, different UEs may be grouped to transmit (using differentfrequency resources) and perform measurements together based at least inpart on the mixed interference measurement dynamic subframe type. Forexample, a first UE may transmit SRS in a subset of SRS regions ofsubframe 555-a (e.g., SRS regions 575 transmitted in SRS regions 1 and2) using a first set of frequency resources. A second UE maysimultaneously transmit in a subset of SRS regions of subframe 555-b(e.g., SRS regions 580 in SRS regions 1 and 2) using a different set offrequency resources. The first and second UE may perform measurementsduring other times of measurement region 570, or may transmit additionalSRS (e.g., in coordination with other UEs) using different sets offrequency resources. The network access device may then schedule a ULcontrol region 595 in each of the subframes 500 following a guard period590. In some examples, subframes 550 may have a self-contained mixedinterference measurement dynamic subframe structure (e.g., a subframestructure in which all transmissions during the subframe are ACK'd orNACK'd during the subframe).

A mixed interference measurement dynamic subframe type may be indicatedin various ways. For example, an indication of mixed interferencemeasurement dynamic subframe type may be embedded in a reference signal.As another example, an indication of a mixed interference measurementdynamic subframe type may be transmitted in a subframe type indicatorchannel, as described, for example, with reference to FIG. 7 . As yetanother example, a mixed interference measurement dynamic subframe typemay be indicated by transmitting a type of DCI corresponding to thedistributed scheduling dynamic subframe type.

FIG. 6 shows an example of a subframe 600 associated with a distributedscheduling dynamic subframe type, in accordance with one or more aspectsof the present disclosure. In some examples, a wireless communicationsystem may include distributed scheduling techniques for a subset of UEs(i.e., scheduling may not be centralized at a network access device,even when the network access device is a part of the network). As aresult, the scheduling of dynamic subframes for contention-based access(e.g., based on request-to-send (RTS)-CTS signaling, node discovery,etc.) may be dynamically signaled by a network access device. In somecases, a distributed scheduling dynamic subframe type may be selectedfor subframe 600, by a network access device such as a base station,based at least in part on a traffic condition, such as a UL/DL trafficratio. Subframe 600 may illustrate an example of a dynamic subframe typescheduled for UEs, which may be examples of MTC-type UEs. In someexamples, the network access device and UEs that communicate usingsubframe 600 may be examples of aspects of the network access devices105 and UEs 115 described with reference to FIG. 1 .

Subframe 600 may begin with a control region (e.g., PDCCH 610)transmitted by the wireless access device. In some cases, PDCCH 610 mayinclude an indication, to UEs that may transmit or receive data insubframe 600, of the distributed scheduling dynamic subframe type ofsubframe 600. For example, a mixed interference measurement dynamicsubframe type associated with subframes 550 may be transmitted to UEs ina temporally first symbol period of a two (or more) symbol period DLcontrol region. In some cases, PDCCH 610 may include assignmentinformation for a relay UE, assignment information for an end device UE,and/or data slot partition information of a serving network accessdevice.

Following PDCCH 610, the network access device may schedule one or morepartitioned regions within subframe 600, such as RTS/CTS/Data/ACKregions 620, for use by one or more UEs. In some examples,RTS/CTS/Data/ACK regions 620 may enable the use of RTS and CTS channelclearing techniques to enable the transmission of data or ACK/NACKwithin the same RTS/CTS/Data/ACK region 620. In some cases, theRTS/CTS/Data/ACK regions may include a gap during which there are notransmissions. The RTS/CTS/Data/ACK regions 620 may be followed by acommon UL burst 630. The UL burst 630 may, for example, be used totransmit an indication of subsequent traffic and/or request additionalresources. In some examples, subframe 600 may have a self-containeddistributed scheduling dynamic subframe structure (e.g., a subframestructure in which all transmissions during the subframe are ACK'd orNACK'd during the subframe).

A distributed scheduling dynamic subframe type may be indicated invarious ways. For example, an indication of a distributed schedulingdynamic subframe type may be embedded in a reference signal. As anotherexample, an indication of a distributed scheduling dynamic subframe typemay be transmitted in a subframe type indicator channel, as described,for example, with reference to FIG. 7 . As yet another example, adistributed scheduling dynamic subframe type may be indicated bytransmitting a type of DCI corresponding to the distributed schedulingdynamic subframe type.

FIG. 7 is a flow chart illustrating an example of a method 700 forindicating a dynamic subframe type in a subframe type indicator channel,in accordance with one or more aspects of the present disclosure. Insome examples, the method 700 may be performed by a network accessdevice, such as one of the network access devices 105 described withreference to FIG. 1 .

The method 700 begins with the receipt of a dynamic subframe typeindicator 705. The dynamic subframe type indicator 705 may in someexamples include one or two bits of information (e.g., a first bitindicating a UL data transmission direction or a DL data transmissiondirection and/or a second bit indicating a half-duplex data transmissionor a full-duplex data transmission). In other examples, the dynamicsubframe type indicator 705 may carry more bits to specify a subset ofthe attributes of the subframe as described above (e.g., subframenumerology). The method 700 may encode and scramble the dynamic subframetype indicator 705 at blocks 710 and 715. For example, the dynamicsubframe type indicator 705 may be block encoded at block 710 and binaryscrambled at block 715. In some examples, the binary scrambling may becell-specific, and in some examples may be based on a gold sequenceinitialized with a subframe number and a cell identifier (ID). In someexamples, the encoding and processing at blocks 710 and 715 may besimilar to the encoding and processing of a physical channel formatindicator channel (PCFICH) in an LTE/LTE-A network.

At block 720, the dynamic subframe type indicator 705 may be modulated(e.g., quadrature phase shift keying (QPSK) modulated). At block 725,the dynamic subframe type indicator 705 may be mapped to tones. At block730, the dynamic subframe type indicator 705 may be orthogonalfrequency-division multiplexing (OFDM) modulated on a subframe typeindicator channel. As previously described, the dynamic subframe typeindicator 705 may, in some examples, be transmitted over a narrow bandand/or one symbol period (e.g., one OFDM symbol period).

FIG. 8A shows an example timeline 800 of operations performed by anetwork access device for a subframe 805 associated with a DL-centricdynamic subframe type, in accordance with one or more aspects of thepresent disclosure. In some examples, the network access device may bean example of one of the network access devices 105 (e.g., an eNB, anANC, a RH, or a base station) described with reference to FIG. 1 .

At a time T-eNB-FrameTick, a modem of the network access device may senda frame tick indication to a MAC layer, which may trigger processing atthe MAC layer. Because the dynamic subframe type for the next subframe(e.g., subframe 805) is a DL-centric dynamic subframe type, the MAClayer may start computation of DL assignments (and some UL grants) for aset of one or more UEs connected to the network access device.

At a time T-eNB-Grant, the MAC layer may send the DL grants (and ULgrants) to the modem for all scheduled UEs. In some examples, the MAClayer may send retransmission (ReTx) indicators (e.g., indicators ofwhether data to be transmitted to a UE is new data, an ReTx, or anautomatic ReTx (AutoReTx)) along with the DL grants. At a timeT-eNB-DLData, the MAC layer may start direct memory access (DMA)transfers of DL data (e.g., a transfer of all transport blocks (TBs) forall scheduled UEs) to the modem. At a time T-eNB-DLAck, the modem maysend a DL ACK or NACK. In some cases, a UL control region may optionallyinclude UL data, and at a time T-eNB-ULData, the modem may send UL data(TBs for all scheduled UEs) received during the UL control region (e.g.,during symbol 14) of subframe 805 to the MAC layer.

FIG. 8B shows an example timeline 850 of operations performed by anetwork access device for a subframe 855 associated with a UL-centricdynamic subframe type, in accordance with one or more aspects of thepresent disclosure. In some examples, the network access device may bean example of one of the network access devices 105 (e.g., an eNB, anANC, a RH, or a base station) described with reference to FIG. 1 .

At a time T-eNB-FrameTick, a modem of the network access device may senda frame tick indication to a MAC layer. This may trigger processing atthe MAC layer. Because the dynamic subframe type for the next subframe(e.g., subframe 855) is a UL-centric dynamic subframe type, the MAClayer may start computation of UL grants for a set of one or more UEsconnected to the network access device. At a time T-eNB-Grant, the MAClayer may send the UL grants to the modem for all scheduled UEs. In someexamples, the MAC layer may send ReTx indicators along with the ULgrants. In some examples, a DL control region may optionally include DLdata for one or more scheduled UEs. At a time T-eNB-ULData, the modemmay send UL data (TBs for all scheduled UEs) received during thesubframe 855 to the MAC layer.

Given the similarity between the MAC layer processing across subframesassociated with DL-centric dynamic subframe types and UL-centric dynamicsubframe types, the MAC layer processor at a network access device(e.g., an eNB) can handle dynamic UL and DL subframe operations.Furthermore, a MAC layer processor at a network access device may beconfigured to handle simultaneous UL and DL transmissions for afull-duplex dynamic subframe type (not shown).

FIG. 9A shows an example timeline 900 of operations performed by a UEfor a subframe 905 associated with a DL-centric dynamic subframe type,in accordance with one or more aspects of the present disclosure. Insome examples, the UE may be an example of one of the UEs 115 describedwith reference to FIG. 1 .

At a time T-UE-FrameTick, a modem of the UE may send a frame tickindication to a MAC layer, which may trigger processing at the MAClayer. The MAC layer may initially assume that the dynamic subframe typefor the next subframe (e.g., subframe 905) is a UL-centric dynamicsubframe type. If it is later determined that the dynamic subframe typeof the subframe 905 is a DL-centric dynamic subframe type, the MAC layermay perform no further action for the subframe 905. The processing atthe MAC layer may include estimation of a minimum expected UL grant(e.g., a grant prediction). At a time T-UE-ULData 1, the MAC layer maysend UL data (e.g., UL Data 1) to the modem. The UL Data 1 may includean estimated minimum TB size (e.g., the grant prediction) for thesubframe 905.

At a time T-UE-Grant, the modem may send DL assignment or UL grantinformation received in one or more symbols of a DL control region ofthe subframe 905 to the MAC layer. Upon the MAC layer identifying a DLassignment for a DL-centric subframe type, then the MAC layer may assumethat the TB sent in UL Data 1 command has been discarded by the modem.If the MAC layer identifies a UL grant for a DL-centric dynamic subframetype, the MAC layer may begin creating a TB. At a time T-UE-ULData, theMAC layer may send UL data including a TB for transmission during a ULcontrol part of the subframe 805. At the time T-UE-DLData, the modem maysend a DL data indication indicating a TB has been received.

FIG. 9B shows an example timeline 950 of operations performed by a UEfor a subframe 955 associated with a UL-centric dynamic subframe type,in accordance with one or more aspects of the present disclosure. Insome examples, the UE may be an example of one of the UEs 115 describedwith reference to FIG. 1 .

When a dynamic subframe type indicator is received by a UE during afirst symbol period of a two symbol period DL control region, the twosymbol period DL control region may allow time for processing (e.g., PHYlayer and/or modem processing) of the received subframe type indicator.At a time T-UE-FrameTick, a modem of the UE may send a frame tickindication to a MAC layer. This may trigger processing at the MAC layer.The MAC layer may initially assume that the dynamic subframe type forthe next subframe (e.g., subframe 955) is a UL-centric dynamic subframetype. If it is later determined that the dynamic subframe type of thesubframe 955 is a DL-centric dynamic subframe type, the MAC layer mayperform no further action for the subframe 955. The processing at theMAC layer may include estimation of a minimum expected UL grant (e.g., agrant prediction).

At a time T-UE-ULData1, the MAC layer may send UL data (e.g., UL Data 1)to the modem. The UL Data 1 may include an estimated minimum TB size(e.g., the grant prediction) for the subframe 955. At a time T-UE-Grant,the modem may send DL assignment or UL grant information received in oneor more symbols of a DL control region of the subframe 905 to the MAClayer. Upon the MAC layer identifying a UL grant for a UL-centricdynamic subframe type, then the MAC layer may build the remaining partof a TB for the subframe. At a time T-UE-ULData2, the MAC layer may sendadditional UL data (e.g., UL Data 2) to the modem, to complete a TB forthe subframe 955.

As discussed above, a two-symbol control region can provide the UE timefor PHY layer/modem processing. For example, the UE may perform (orcomplete) reference signal processing and channel estimation, anddynamic subframe type indicator demodulation and decoding, during thesecond symbol period of the DL control region. For a DL-centricsubframe, DCI for DL data (e.g., a DL assignment) may be processed anddecoded during receipt of the DL control region. For a DL-centricsubframe having a structure in which a demodulation reference signal(DMRS) is transmitted in the first and/or second symbol period (e.g., inwhich the DMRS is FDM'd within the DL control region), and in someexamples, the UE may start to process the DMRS from buffered samples assoon as the DL assignment is decoded. In a DL-centric subframe, theremay be no need to switch RF direction. For a UL-centric subframe, DCIfor UL data (e.g., a UL grant) may be processed and decoded duringreceipt of the DL control region. In some examples, the UE may start toprepare a UL data transmission for at least a first symbol period assoon as the UL grant is decoded. The preparation of UL data may berelaxed when something else (e.g., a DMRS pilot signal, or a common ULburst (e.g., a UL burst carrying unscheduled UL transmission, such as asounding reference signal (SRS))) can be transmitted before the firstsymbol period of the UL data transmission.

FIG. 10 illustrates an example of resources and UE process timing for asubframe 1000 associated with a DL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure. In someexamples, FIG. 10 may represent aspects of processing performed by amodem of a UE 115 described with reference to FIG. 1 .

In the example of FIG. 10 , a DL portion 1005 of the subframe 1000 maybe received at a UE, followed by a guard period and UL portion 1010 ofthe subframe. The DL portion 1005 received at the UE in this example mayinclude a temporally first symbol period that may include referencesignal (e.g., CRS) pilot resource elements (REs) 1025, control symbolREs 1030 (including a dynamic subframe type indicator) embedded with thereference signal pilot REs 1025, and DMRS REs 1040 and 1045. The controlsymbol REs 1030 may include physical DL control channel (PDCCH)information that includes a resource allocation and processingparameters such as a modulation and coding scheme (MCS), new dataindicator (NDI), and redundancy version (RV), for data symbols 1050. Atemporally second symbol period received at the UE in this example mayinclude other control symbol REs 1035 and DMRS REs 1040 and 1045. Insome examples, other control symbol REs 1035 may be included in controlbandwidth but may not contain PDCCH information. After data symbols1050, the subframe 1000 may include a guard period, and a UL pilot 1055and UL ACK/NACK symbol period 1060 in the UL portion 1010. The subframe1000 may conclude with a final guard period.

During time period 1065, a UE may process the reference signal anddynamic subframe type indicator received in the first symbol period ofthe subframe 1000. At this point, the dynamic subframe type may beunknown. After the dynamic subframe type is known, the UE may decode thePDCCH and search for a DL assignment. This may occur during time period1070. Upon decoding a DL assignment, the resource block (RB) allocationfor the DL assignment may be known, and DMRS processing may begin (e.g.,during time period 1075). Alternatively, DMRS processing may begin priorto knowing the RB allocation. However, this may waste processingresources by processing of unallocated RBs. Following DMRS processing,the data region of the DL portion 1005 may be processed (e.g., duringtime period 1080). Because data may be transmitted during the temporallythird and fourth symbol periods of the subframe 1000, some catching upin terms of data symbol processing may be performed (e.g., processingtwelve symbols in about the time of eleven symbols). However, when PDCCHand DMRS can be fit into the second symbol period, no catching up ofdata symbol processing may be needed. In FIG. 10 , a cyclic prefix (CP)may be a part of each symbol, and is therefore not shown explicitly.

FIG. 11 illustrates an example of resources and UE process timing for asubframe 1100 associated with a UL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure. In someexamples, FIG. 11 may represent aspects of processing performed by amodem of a UE 115 described with reference to FIG. 1 .

In the example of FIG. 11 , a DL portion 1110 of the subframe 1100 maybe received at a UE, followed by a guard period 1115 and a UL portion1120 of the subframe 1100. The DL portion 1110 received at the UE inthis example may include a temporally first symbol period that mayinclude reference signal pilot REs 1125, and control symbol REs 1130(including a dynamic subframe type indicator) embedded within thereference signal pilot REs 1125. The control symbol REs 1130 may alsoinclude a UL grant for the UE. A temporally second symbol periodreceived at the UE in this example may include additional control symbolREs 1135. The additional control symbol REs 1135 may include PDCCHinformation that includes a resource allocation and processingparameters such as an MCS for data symbols 1150. In some examples,additional control symbol REs 1135 may be included in control bandwidthbut may not contain PDCCH information. Following the guard period 1115,DMRS REs 1140 and 1145 may be transmitted in the first two UL symbolperiods of a UL data region, followed by UL data symbols 1150.

During a time period 1165, a UE may process the reference signal anddynamic subframe type indicator received in the first symbol period ofthe subframe 1100. At this point, the dynamic subframe type may beunknown. After the dynamic subframe type is known, the UE may decode thePDCCH and search for a UL grant. This may occur during the time period1170. RF switching, from receive mode to transmit mode, may also occurduring time period 1170. Upon decoding a UL grant, the RB allocation forthe UL grant is known, and DMRS processing/transmission may begin (e.g.,during the time period 1175). Alternatively, partial pre-processing ofthe DMRS may begin prior to knowing the RB allocation. However, this maywaste processing resources by processing DMRS for unallocated RBs. ULdata symbol processing (e.g., encoding and modulation for a first one ormore data symbols) may also begin during time period 1175. FollowingDMRS processing, the data region of the UL portion 1120 may be processedand transmitted (e.g., during time period 1180). In FIG. 11 , a CP maybe a part of each symbol, and is therefore not shown explicitly.

FIG. 12 illustrates an example of resources and UE process timing for asubframe 1200 associated with a UL-centric dynamic subframe type, inaccordance with one or more aspects of the present disclosure. In someexamples, FIG. 12 may represent aspects of processing performed by amodem of a UE 115 described with reference to FIG. 1 .

In the example of FIG. 12 , a DL portion 1210 of the subframe 1200 maybe received at a UE, followed by a guard period 1215, a non-timecritical UL burst 1255, and a UL portion 1220 of the subframe 1200. TheDL portion 1210 received at the UE in this example may include atemporally first symbol period that may include reference signal pilotREs 1225, and control symbol REs 1230 (including a dynamic subframe typeindicator) embedded within the reference signal pilot REs 1225. Thecontrol symbol REs 1230 may also include a UL grant for the UE. Atemporally second symbol period received at the UE in this example mayinclude additional control symbols 1235.

Following the guard period 1215, the non-time critical UL burst 1255 maybe transmitted in a first symbol period of a UL data region. Thenon-time critical UL burst 1255 may be prepared in advance, and mayprovide the UE with additional processing time to prepare a DMRS and/orUL data symbols 1250 for transmission in the UL data region (or ULportion 1220). In some examples, the non-time critical UL burst 1255 mayinclude an unscheduled (or a-priori scheduled) UL transmission, such asan SRS or channel quality indicator (CQI). DMRS REs 1240 and 1245 may betransmitted in the second and third UL symbol periods of the UL dataregion, followed by UL data symbols 1250. The additional control symbolREs 1235 may include PDCCH information that includes a resourceallocation and processing parameters such as an MCS for data symbols1250. In some examples, additional control symbol REs 1235 may beincluded in control bandwidth but may not contain PDCCH information.

During a time period 1265, a UE may process the reference signal anddynamic subframe type indicator received in the first symbol period ofthe subframe 1200. At this point, the dynamic subframe type is unknown.After the dynamic subframe type is known, the UE may decode the PDCCHand search for a UL grant. This may occur during the time period 1270,which may be longer than the time period 1170 described with referenceto FIG. 11 because of transmission of the non-time critical UL burst1255. RF switching, from receive mode to transmit mode, may also occurduring time period 1170. Upon decoding a UL grant, the RB allocation forthe UL grant is known, and DMRS processing/transmission may begin (e.g.,during the time period 1275). Alternatively, partial pre-processing ofthe DMRS may begin prior to knowing the RB allocation. However, this maywaste processing resources because of DMRS processing for unallocatedRBs. UL data symbol processing (e.g., encoding and modulation for afirst one or more data symbols) may also begin during time period 1275.Following DMRS processing, the data region of the UL portion 1220 may beprocessed and transmitted (e.g., during time period 1280). In FIG. 12 ,a cyclic prefix (CP) may be a part of each symbol, and is therefore notshown explicitly.

Because HARQ feedback is dependent on the direction of data transmissionin a subframe, the selection of a dynamic subframe type for a subframemay be used as a basis for allocating HARQ resources for the subframe.When a subframe is self-contained, HARQ resources may be allocatedwithin the subframe. For a subframe associated with a DL-centric dynamicsubframe type, a HARQ transmission period (e.g., a UL transmissionperiod) may be allocated for the subframe at an end of the subframe. Fora subframe associated with a UL-centric dynamic subframe type, a HARQtransmission period (e.g., a DL transmission period) may be allocatedfor the subframe at an end of the subframe, or at least one HARQtransmission resource for the subframe may be allocated in a DL controlregion of a subsequent subframe.

When a subframe includes at least one DL data region and at least one ULdata region, at least one DL HARQ transmission resource may be allocatedfor the subframe and at least one UL HARQ transmission resource may beallocated for the subframe in the subframe (or the at least one DL HARQtransmission resource may be allocated in a DL control region of asubsequent subframe).

FIG. 13 shows a block diagram 1300 of an apparatus 1305 for use inwireless communication, in accordance with one or more aspects of thepresent disclosure. The apparatus 1305 may be an example of aspects ofone or more of the network access devices 105 described with referenceto FIG. 1 . The apparatus 1305 may also be, or include, a processor. Theapparatus 1305 may include a receiver 1310, a wireless communicationmanager 1320, or a transmitter 1330. Each of these components may be incommunication with each other.

The components of the apparatus 1305 may, individually or collectively,be implemented using one or more application-specific integratedcircuits (ASICs) adapted to perform some or all of the applicablefunctions in hardware. Alternatively, the functions may be performed byone or more other processing units (or cores), on one or more integratedcircuits (ICs). In some other examples, other types of integratedcircuits may be used (e.g., Structured/Platform ASICs, FieldProgrammable Gate Arrays (FPGAs), a System-on-Chip (SoC), and/or othertypes of semi-custom ICs), which may be programmed in any manner knownin the art. The functions of each component may also be implemented, inwhole or in part, with instructions stored in a memory, formatted to beexecuted by one or more general or application-specific processors.

In some examples, the receiver 1310 may include at least one RFreceiver, such as at least one RF receiver operable to receivetransmissions over one or more radio frequency spectrum bands. In someexamples, the one or more radio frequency spectrum bands may be used forLTE/LTE-A or 5G communications, as described, for example, withreference to FIGS. 1 through 12 . The receiver 1310 may be used toreceive various types of data or control signals (i.e., transmissions)over one or more communication links of a wireless communication system,such as one or more communication links of the wireless communicationsystem 100 described with reference to FIG. 1 .

In some examples, the transmitter 1330 may include at least one RFtransmitter, such as at least one RF transmitter operable to transmitover one or more radio frequency spectrum bands. In some examples, theone or more radio frequency spectrum bands may be used for LTE/LTE-A or5G communications, as described, for example, with reference to FIGS. 1through 12 . The transmitter 1330 may be used to transmit various typesof data or control signals (i.e., transmissions) over one or morecommunication links of a wireless communication system, such as one ormore communication links of the wireless communication system 100described with reference to FIG. 1 .

In some examples, the wireless communication manager 1320 may be used tomanage one or more aspects of wireless communication for the apparatus1305. In some examples, part of the wireless communication manager 1320may be incorporated into or shared with the receiver 1310 or thetransmitter 1330. In some examples, the wireless communication manager1320 may be an example of aspects of the network access device wirelesscommunication manager described with reference to FIG. 1 . In someexamples, the wireless communication manager 1320 may include a trafficratio identifier 1335, a dynamic subframe type selector 1340, or adynamic subframe type indication manager 1345.

The traffic ratio identifier 1335 may be used to identify a UL/DLtraffic ratio associated with data to be transmitted between a networkaccess device including the apparatus 1305 and at least one UE. In someexamples, the UL/DL traffic ratio may include a ratio of traffic queuedfor transmission to the network access device and traffic queued fortransmission to at least one UE.

The dynamic subframe type selector 1340 may be used to select, based atleast in part on a traffic condition (e.g., the UL/DL traffic ratio), adynamic subframe type of a TDD subframe. In some examples, the dynamicsubframe type may be selected from a set of dynamic subframe typesincluding two or more of: a DL-centric dynamic subframe type, aUL-centric dynamic subframe type, a bi-directional dynamic subframetype, a full-duplex dynamic subframe type, a dynamic switch dynamicsubframe type, a mixed interference measurement dynamic subframe type,or a distributed scheduling dynamic subframe type.

The dynamic subframe type indication manager 1345 may be used toindicate the dynamic subframe type in a TDD header of the subframe. Insome examples, the dynamic subframe type may be indicated within atemporally first symbol period of the subframe. In some examples,indicating the dynamic subframe type may include at least one of:embedding an indication of the dynamic subframe type in a referencesignal, transmitting the indication of the dynamic subframe type in asubframe type indicator channel, or transmitting a type of DCIcorresponding to the dynamic subframe type. In some examples, indicatingthe dynamic subframe type may include at least one of broadcasting thedynamic subframe type to UEs associated with a cell, or unicasting thedynamic subframe type to a subset of UEs associated with the cell. Insome examples, indicating the dynamic subframe type may includetransmitting an indication of the dynamic subframe type within a narrowband of frequencies of a system bandwidth, as described with referenceto FIG. 3 . In some examples, indicating the dynamic subframe type mayinclude transmitting at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction, or a secondbit indicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof.

FIG. 14 shows a block diagram 1400 of a wireless communication manager1320-b for use in wireless communication, in accordance with one or moreaspects of the present disclosure. The wireless communication manager1320-b may be an example of aspects of the wireless communicationmanager 1320 described with reference to FIG. 1 or 13 .

The components of the wireless communication manager 1320-b may,individually or collectively, be implemented using one or more ASICsadapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits. In someother examples, other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, FPGAs, a SoC, and/or other types ofSemi-Custom ICs), which may be programmed in any manner known in theart. The functions of each component may also be implemented, in wholeor in part, with instructions stored in a memory, formatted to beexecuted by one or more general or application-specific processors.

In some examples, the wireless communication manager 1320-b may be usedto manage one or more aspects of wireless communication for a UE orapparatus, such as one of the network access devices 105 or apparatuses1305 described with reference to FIG. 1 or 13 . In some examples, partof the wireless communication manager 1320-b may be incorporated into orshared with a receiver or a transmitter (e.g., the receiver 1310 or thetransmitter 1330 described with reference to FIG. 13 ). In someexamples, the wireless communication manager 1320-b may include atraffic ratio identifier 1335-a, a dynamic subframe type selector1340-a, a TDD data region scheduler 1405, a guard period scheduler 1410,a HARQ resource allocator 1415, a TDD header transmission manager 1420,a data transmission/reception manager 1430, or a HARQ manager 1435.

The traffic ratio identifier 1335 may be used to identify a UL/DLtraffic ratio associated with data to be transmitted between a networkaccess device including the wireless communication manager 1320-b and atleast one UE. In some examples, the UL/DL traffic ratio may include aratio of traffic queued for transmission to the network access deviceand traffic queued for transmission to the at least one UE.

The dynamic subframe type selector 1340 may be used to select, based atleast in part on a traffic condition (e.g., the UL/DL traffic ratio), adynamic subframe type of a TDD subframe. In some examples, the dynamicsubframe type may be selected from a set of dynamic subframe typesincluding two or more of: a DL-centric dynamic subframe type, aUL-centric dynamic subframe type, a bi-directional dynamic subframetype, a full-duplex dynamic subframe type, a dynamic switch dynamicsubframe type, a mixed interference measurement dynamic subframe type,or a distributed scheduling dynamic subframe type.

The TDD data region scheduler 1405 may be used to schedule a data regionof the TDD subframe based at least in part on the selected dynamicsubframe type. The guard period scheduler 1410 may be used to schedule aguard period, between a DL control region of the subframe and the dataregion, when the selected dynamic subframe type is associated with adata region having a UL portion (which UL portion may in some examplesinclude the entire data region).

The HARQ resource allocator 1415 may be used to allocate a HARQtransmission period for the subframe at an end of the subframe, allocateat least one HARQ transmission resource for the subframe in a DL controlregion of a subsequent subframe, or allocate at least one DL HARQtransmission resource for the subframe and at least one UL HARQtransmission resource for the subframe in the subframe.

The TDD header transmission manager 1420 may be used to transmit a TDDheader of the subframe. The TDD header may include the DL control regionand an indication of the dynamic subframe type. In some examples, theTDD header transmission manager 1420 may include a DL control regiontransmission manager 1425 to manage transmission of the DL controlregion, or a dynamic subframe type indication manager 1345-a to managetransmission of the indication of the dynamic subframe type. In someexamples, the indication of the dynamic subframe type may be transmittedin the DL control region. In some examples, the DL control region may betransmitted within a temporally first symbol period of the subframe, orwithin the temporally first symbol period of the TDD subframe and atemporally second symbol period of the TDD subframe. In some examples,the dynamic subframe type may be indicated within the temporally firstsymbol period of the TDD subframe.

In some examples, indicating the dynamic subframe type may include atleast one of: embedding an indication of the dynamic subframe type in areference signal, transmitting the indication of the dynamic subframetype in a subframe type indicator channel, or transmitting a type of DCIcorresponding to the dynamic subframe type. In some examples, indicatingthe dynamic subframe type may include at least one of broadcasting thedynamic subframe type to UEs associated with a cell, or unicasting thedynamic subframe type to a subset of UEs associated with the cell. Insome examples, indicating the dynamic subframe type may includetransmitting an indication of the dynamic subframe type within a narrowband of frequencies of a system bandwidth, as described with referenceto FIG. 3 . In some examples, indicating the dynamic subframe type mayinclude transmitting at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction, or a secondbit indicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof. The data transmission/receptionmanager 1430 may be used to transmit and/or receive data in thescheduled data region. The HARQ manager 1435 may be used to transmitand/or receive at least one HARQ transmission on a HARQ resourcescheduled by the HARQ resource allocator 1415.

FIG. 15 shows a block diagram 1500 of an apparatus 1515 for use inwireless communication, in accordance with one or more aspects of thepresent disclosure. The apparatus 1515 may be an example of aspects ofone or more of the UEs 115 described with reference to FIG. 1 . Theapparatus 1515 may also be or include a processor. The apparatus 1515may include a receiver 1510, a wireless communication manager 1520-a, ora transmitter 1530. Each of these components may be in communicationwith each other.

The components of the apparatus 1515 may, individually or collectively,be implemented using one or more ASICs adapted to perform some or all ofthe applicable functions in hardware. Alternatively, the functions maybe performed by one or more other processing units (or cores), on one ormore integrated circuits. In some other examples, other types ofintegrated circuits may be used (e.g., Structured/Platform ASICs, FPGAs,a SoC, and/or other types of semi-custom ICs), which may be programmedin any manner known in the art. The functions of each component may alsobe implemented, in whole or in part, with instructions stored in amemory, formatted to be executed by one or more general orapplication-specific processors.

In some examples, the receiver 1510 may include at least one RFreceiver, such as at least one RF receiver operable to receivetransmissions over one or more radio frequency spectrum bands. In someexamples, the one or more radio frequency spectrum bands may be used forLTE/LTE-A or 5G communications, as described, for example, withreference to FIGS. 1 through 12 . The receiver 1510 may be used toreceive various types of data or control signals (i.e., transmissions)over one or more communication links of a wireless communication system,such as one or more communication links of the wireless communicationsystem 100 described with reference to FIG. 1 .

In some examples, the transmitter 1530 may include at least one RFtransmitter, such as at least one RF transmitter operable to transmitover one or more radio frequency spectrum bands. In some examples, theone or more radio frequency spectrum bands may be used for LTE/LTE-A or5G communications, as described, for example, with reference to FIGS. 1through 12 . The transmitter 1530 may be used to transmit various typesof data or control signals (i.e., transmissions) over one or morecommunication links of a wireless communication system, such as one ormore communication links of the wireless communication system 100described with reference to FIG. 1 .

In some examples, the wireless communication manager 1520-a may be usedto manage one or more aspects of wireless communication for theapparatus 1515. In some examples, part of the wireless communicationmanager 1520-a may be incorporated into or shared with the receiver 1510or the transmitter 1530. In some examples, the wireless communicationmanager 1520-a may be an example of aspects of the UE wirelesscommunication manager 1520 described with reference to FIG. 1 . In someexamples, the wireless communication manager 1520-a may include adynamic subframe type identifier 1535 or a data transmission/receptionmanager 1540.

The dynamic subframe type identifier 1535 may be used to identify, in aTDD header of a TDD subframe, an indication of a dynamic subframe typeof the TDD subframe. In some examples, the dynamic subframe type mayinclude: a DL-centric dynamic subframe type, a UL-centric dynamicsubframe type, a bi-directional dynamic subframe type, a full-duplexdynamic subframe type, a dynamic switch dynamic subframe type, a mixedinterference measurement dynamic subframe type, or a distributedscheduling dynamic subframe type. In some examples, the dynamic subframetype may be identified within a temporally first symbol period of thesubframe. In some examples, the dynamic subframe type may be identifiedbased at least in part on at least one of: an indication of the dynamicsubframe type embedded in a reference signal, an indication of thedynamic subframe type received in a subframe type indicator channel, ora type of received DCI.

In some examples, the dynamic subframe type may be received in at leastone of broadcast control information or unicast control information. Insome examples, identifying the dynamic subframe type may includeidentifying an indication of the dynamic subframe type within a narrowband of frequencies of a system bandwidth, as described with referenceto FIG. 3 . In some examples, identifying the dynamic subframe type mayinclude receiving at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction, or a secondbit indicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof. The data transmission/receptionmanager 1540 may be used to transmit data or receiving data in a dataregion of the subframe based at least in part on the dynamic subframetype.

FIG. 16 shows a block diagram 1600 of a wireless communication manager1520-b for use in wireless communication, in accordance with one or moreaspects of the present disclosure. The wireless communication manager1520-a may be an example of aspects of the wireless communicationmanager 1520 described with reference to FIG. 1 or 15 .

The components of the wireless communication manager 1520-a may,individually or collectively, be implemented using one or more ASICsadapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits. In someother examples, other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, FPGAs, a SoC, and/or other types ofsemi-custom ICs), which may be programmed in any manner known in theart. The functions of each component may also be implemented, in wholeor in part, with instructions stored in a memory, formatted to beexecuted by one or more general or application-specific processors.

In some examples, the wireless communication manager 1520-a may be usedto manage one or more aspects of wireless communication for a UE orapparatus, such as one of the UEs 115 or apparatuses 1515 described withreference to FIG. 1 or 15 . In some examples, part of the wirelesscommunication manager 1520-a may be incorporated into or shared with areceiver or a transmitter (e.g., the receiver 1510 or the transmitter1530 described with reference to FIG. 15 ). In some examples, thewireless communication manager 1520-a may include a header processor1605, a guard period manager 1610, a data transmission/reception manager1540, or a HARQ manager 1615.

The header processor 1605 may be used to receive a TDD header of a TDDsubframe. The TDD header may include a DL control region and anindication of a dynamic subframe type of the TDD subframe. In someexamples, the indication of the dynamic subframe type may be received inthe DL control region. In some examples, the DL control region may bereceived within a temporally first symbol period of the TDD subframe, orwithin the temporally first symbol period of the TDD subframe and atemporally second symbol period of the TDD subframe.

In some examples, the header processor 1605 may include a dynamicsubframe type identifier 1535. The dynamic subframe type identifier 1535may be used to identify, in the TDD header (and in some examples, in theDL control region), the indication of the dynamic subframe type. In someexamples, the dynamic subframe type may include: a DL-centric dynamicsubframe type, a UL-centric dynamic subframe type, a bi-directionaldynamic subframe type, a full-duplex dynamic subframe type, a dynamicswitch dynamic subframe type, a mixed interference measurement dynamicsubframe type, or a distributed scheduling dynamic subframe type. Insome examples, the dynamic subframe type may be identified within atemporally first symbol period of the TDD subframe.

In some examples, the dynamic subframe type may be identified based atleast in part on at least one of: an indication of the dynamic subframetype embedded in a reference signal, an indication of the dynamicsubframe type received in a subframe type indicator channel, or a typeof received DCI. In some examples, the dynamic subframe type may bereceived in at least one of broadcast control information or unicastcontrol information. In some examples, identifying the dynamic subframetype may include identifying an indication of the dynamic subframe typewithin a narrow band of frequencies of a system bandwidth, as describedwith reference to FIG. 3 . In some examples, identifying the dynamicsubframe type may include receiving at least one of: a first bitindicating a UL data transmission direction or a DL data transmissiondirection, or a second bit indicating a half-duplex data transmission ora full-duplex data transmission, or a combination thereof.

The guard period manager 1610 may be used to refrain from transmittingduring a guard period, between the DL control region and the dataregion, when the identified dynamic subframe type is associated with adata region having a UL portion (which UL portion may in some examplesinclude the entire data region). The data transmission/reception manager1540 may be used to transmit data or receiving data in a data region ofthe subframe based at least in part on the dynamic subframe type.

The HARQ manager 1615 may be used to identify an allocation of a HARQtransmission period for the TDD subframe at an end of the TDD subframe,an allocation of at least one HARQ transmission resource for thesubframe in a DL control region of a subsequent TDD subframe, or anallocation of at least one DL HARQ transmission resource for the TDDsubframe and at least one UL HARQ transmission resource for the TDDsubframe in the TDD subframe. The HARQ manager 1615 may also be used totransmit and/or receive at least one HARQ transmission on an allocatedHARQ resource.

FIG. 17 shows a block diagram 1700 of a network access device 105-d foruse in wireless communication, in accordance with one or more aspects ofthe present disclosure. In some examples, the network access device105-d may be an example of one or more aspects of a network accessdevice (e.g., an eNB, an ANC, a RH, or a base station) described withreference to FIG. 1 , or aspects of the apparatus 1305 described withreference to FIG. 13 . The network access device 105-d may be configuredto implement or facilitate at least some of the network access devicetechniques and functions described with reference to FIGS. 1 through 14.

The network access device 105-d may include a base station processor1710, a memory 1720, at least one transceiver (represented bytransceiver(s) 1750), at least one antenna (represented by base stationantenna(s) 1755), or a wireless communication manager 1320-c. Thenetwork access device 105-d may also include one or more of a networkaccess device communicator 1730 or a network communicator 1740. Each ofthese components may be in communication with each other, directly orindirectly, over one or more buses 1735.

The memory 1720 may include random access memory (RAM) or read-onlymemory (ROM). The memory 1720 may store computer-readable,computer-executable code 1725 containing instructions that areconfigured to, when executed, cause the processor 1710 to performvarious functions described herein related to wireless communication,including, for example, identifying a traffic condition associated withdata to be transmitted between a network access device and at least oneUE; selecting, based at least in part on the traffic condition, adynamic subframe type of a TDD subframe; and indicating the dynamicsubframe type in a TDD header of the TDD subframe. Alternatively, thecomputer-executable code 1725 may not be directly executable by theprocessor 1710 but be configured to cause the network access device105-d (e.g., when compiled and executed) to perform various of thefunctions described herein.

The processor 1710 may include an intelligent hardware device, e.g., acentral processing unit (CPU), a microcontroller, an ASIC, etc. Theprocessor 1710 may process information received through thetransceiver(s) 1750, the network access device communicator 1730, or thenetwork communicator 1740. The processor 1710 may also processinformation to be sent to the transceiver(s) 1750 for transmissionthrough the antenna(s) 1755, to the network access device communicator1730, for transmission to one or more other network access devices(e.g., network access device 105-e and network access device 105-f), orto the network communicator 1740 for transmission to a core network1745, which may be an example of one or more aspects of the core network130 described with reference to FIG. 1 . The processor 1710 may handle,alone or in connection with the wireless communication manager 1320-c,various aspects of communicating over (or managing communications over)one or more radio frequency spectrum bands.

The transceiver(s) 1750 may include a modem configured to modulatepackets and provide the modulated packets to the antenna(s) 1755 fortransmission, and to demodulate packets received from the antenna(s)1755. The transceiver(s) 1750 may, in some examples, be implemented asone or more transmitters and one or more separate receivers. Thetransceiver(s) 1750 may support communications in one or more radiofrequency spectrum bands. The transceiver(s) 1750 may be configured tocommunicate bi-directionally, via the antenna(s) 1755, with one or moreUEs or apparatuses, such as one or more of the UEs 115 described withreference to FIG. 1 , or one or more of the apparatus 1515 describedwith reference to FIG. 15 . The network access device 105-d may, forexample, include multiple antennas 1755 (e.g., an antenna array). Thenetwork access device 105-d may communicate with the core network 1745through the network communicator 1740. The network access device 105-dmay also communicate with other network access devices, such as thenetwork access device 105-e and the network access device 105-f, usingthe network access device communicator 1730.

The wireless communication manager 1320-c may be configured to performor control some or all of the techniques or functions described withreference to FIGS. 1 through 14 related to wireless communication overone or more radio frequency spectrum bands. The wireless communicationmanager 1320-c, or portions of it, may include a processor, or some orall of the functions of the wireless communication manager 1320-c may beperformed by the processor 1710 or in connection with the processor1710. In some examples, the wireless communication manager 1320-c may bean example of the wireless communication manager 1320 described withreference to FIG. 1, 13 , or 14.

FIG. 18 shows a block diagram 1800 of a UE 115-a for use in wirelesscommunication, in accordance with one or more aspects of the presentdisclosure. The UE 115-a may be included or be part of a personalcomputer (e.g., a laptop computer, a netbook computer, a tabletcomputer, etc.), a cellular telephone, a PDA, a DVR, an internetappliance, a gaming console, an e-reader, a vehicle, a home appliance, alighting or alarm control system, etc. The UE 115-a may, in someexamples, have an internal power supply (not shown), such as a smallbattery, to facilitate mobile operation. In some examples, the UE 115-amay be an example of aspects of one or more of the UEs 115 describedwith reference to FIG. 1 , or aspects of the apparatus 1515 describedwith reference to FIG. 15 . The UE 115-a may be configured to implementat least some of the UE or apparatus techniques and functions describedwith reference to FIGS. 1 through 16 .

The UE 115-a may include a processor 1810, a memory 1820, at least onetransceiver (represented by transceiver(s) 1830), at least one antenna(represented by antenna(s) 1840), or a wireless communication manager1520-c. Each of these components may be in communication with eachother, directly or indirectly, over one or more buses 1835.

The memory 1820 may include RAM or ROM. The memory 1820 may storecomputer-readable, computer-executable code 1825 containing instructionsthat are configured to, when executed, cause the processor 1810 toperform various functions described herein related to wirelesscommunication, including, for example, identifying, in a TDD header of asubframe, an indication of a dynamic subframe type of the TDD subframe,and transmitting data or receiving data during the TDD subframe based atleast in part on the dynamic subframe type. Alternatively, thecomputer-executable code 1825 may not be directly executable by theprocessor 1810 but be configured to cause the UE 115-a (e.g., whencompiled and executed) to perform various of the functions describedherein.

The processor 1810 may include an intelligent hardware device, e.g., aCPU, a microcontroller, an ASIC, etc. The processor 1810 may processinformation received through the transceiver(s) 1830 or information tobe sent to the transceiver(s) 1830 for transmission through theantenna(s) 1840. The processor 1810 may handle, alone or in connectionwith the wireless communication manager 1520-c, various aspects ofcommunicating over (or managing communications over) one or more radiofrequency spectrum bands.

The transceiver(s) 1830 may include a modem configured to modulatepackets and provide the modulated packets to the antenna(s) 1840 fortransmission, and to demodulate packets received from the antenna(s)1840. The transceiver(s) 1830 may, in some examples, be implemented asone or more transmitters and one or more separate receivers. Thetransceiver(s) 1830 may support communications in one or more radiofrequency spectrum bands. The transceiver(s) 1830 may be configured tocommunicate bi-directionally, via the antenna(s) 1840, with one or moreof the network access devices 105 described with reference to FIG. 1 or17 , or one or more of the apparatus 1305 described with reference toFIG. 13 . While the UE 115-a may include a single antenna, there may beexamples in which the UE 115-a may include multiple antennas 1840.

The wireless communication manager 1520-c may be configured to performor control some or all of the UE or apparatus techniques or functionsdescribed with reference to FIGS. 1 through 16 related to wirelesscommunication over one or more radio frequency spectrum bands. Thewireless communication manager 1520-c, or portions of it, may include aprocessor, or some or all of the functions of the wireless communicationmanager 1520-c may be performed by the processor 1810 or in connectionwith the processor 1810. In some examples, the wireless communicationmanager 1520-c may be an example of the wireless communication manager1520 described with reference to FIG. 1, 15 , or 16.

FIG. 19 is a flow chart illustrating an example of a method 1900 forwireless communication, in accordance with one or more aspects of thepresent disclosure. For clarity, the method 1900 is described below withreference to aspects of a network access device 105 (e.g., an eNB, anANC, an RH, or a base station) described with reference to FIG. 1 or 17, or aspects of the apparatus 1305 described with reference to FIG. 13 ,or aspects of the wireless communication manager 1320 described withreference to FIG. 1, 13, 14 , or 17. In some examples, a network accessdevice may execute one or more sets of codes to control the functionalelements of the network access device to perform the functions describedbelow. Additionally or alternatively, the network access device mayperform one or more of the functions described below usingspecial-purpose hardware.

At block 1905, the method 1900 may include selecting a dynamic subframetype of a TDD subframe. In some examples, the dynamic subframe type maybe selected from a set of dynamic subframe types including two or moreof: a DL-centric dynamic subframe type, a UL-centric dynamic subframetype, a bi-directional dynamic subframe type, a full-duplex dynamicsubframe type, a dynamic switch dynamic subframe type, a mixedinterference measurement dynamic subframe type, or a distributedscheduling dynamic subframe type. The operation(s) at block 1905 may beperformed using the wireless communication manager 1320 described withreference to FIG. 1, 13, 14 , or 17, or the dynamic subframe typeselector 1340 described with reference to FIG. 13 or 14 .

At block 1910, the method 1900 may include indicating the dynamicsubframe type in a TDD header of the TDD subframe. In some examples, thedynamic subframe type may be indicated within a temporally first symbolperiod of the TDD subframe. In some examples, indicating the dynamicsubframe type may include at least one of: embedding an indication ofthe dynamic subframe type in a reference signal, transmitting theindication of the dynamic subframe type in a subframe type indicatorchannel, or transmitting a type of DCI corresponding to the dynamicsubframe type. In some examples, indicating the dynamic subframe typemay include at least one of broadcasting the dynamic subframe type toUEs associated with a cell, or unicasting the dynamic subframe type to asubset of UEs associated with the cell. In some examples, indicating thedynamic subframe type may include transmitting an indication of thedynamic subframe type within a narrow band of frequencies of a systembandwidth, as described with reference to FIG. 3 .

In some cases, the dynamic subframe type may be determined using acombination of the content of the indication (i.e., one or more bits)and any context or mode that has been configured. For example, if theaccess network device 105 and the UEs in communication with the accessnetwork device 105 are configured to support a subset of the dynamicsubframe types, and the subset of dynamic subframe types does not changedynamically, the indication of the dynamic subframe type may specifywhich dynamic subframe type within the subset of dynamic subframe typesis in use. In some examples, indicating the dynamic subframe type mayinclude transmitting at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction, or a secondbit indicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof. The operation(s) at block 1910may be performed using the wireless communication manager 1320 describedwith reference to FIG. 1, 13, 14 , or 17, or the dynamic subframe typeindication manager 1345 described with reference to FIG. 13 or 14 .

Thus, the method 1900 may provide for wireless communication. It shouldbe noted that the method 1900 is just one implementation and that theoperations of the method 1900 may be rearranged or otherwise modifiedsuch that other implementations are possible.

FIG. 20 is a flow chart illustrating an example of a method 2000 forwireless communication, in accordance with one or more aspects of thepresent disclosure. For clarity, the method 2000 is described below withreference to aspects of a network access device 105 (e.g., an eNB, anANC, an RH, or a base station) described with reference to FIG. 1 or 17, or aspects of the apparatus 1305 described with reference to FIG. 13 ,or aspects of the wireless communication manager 1320 described withreference to FIG. 1, 13, 14 , or 17. In some examples, a network accessdevice may execute one or more sets of codes to control the functionalelements of the network access device to perform the functions describedbelow. Additionally or alternatively, the network access device mayperform one or more of the functions described below usingspecial-purpose hardware.

At block 2005, the method 2000 may include identifying a trafficcondition associated with data to be transmitted between a networkaccess device and at least one UE. In some cases, the traffic conditionmay include a UL/DL traffic ratio. In some examples, the UL/DL trafficratio may include a ratio of traffic queued for transmission to thenetwork access device and traffic queued for transmission to the atleast one UE. The operation(s) at block 2005 may be performed using thewireless communication manager 1320 described with reference to FIG. 1,13, 14 , or 17, or the traffic ratio identifier 1335 described withreference to FIG. 13 or 14 .

At block 2010, the method 2000 may include selecting, based at least inpart on the traffic condition, a dynamic subframe type of a subframe. Insome examples, the dynamic subframe type may be selected from a set ofdynamic subframe types including two or more of: a DL-centric dynamicsubframe type, a UL-centric dynamic subframe type, a bi-directionaldynamic subframe type, or a full-duplex dynamic subframe type. Theoperation(s) at block 2010 may be performed using the wirelesscommunication manager 1320 described with reference to FIG. 1, 13, 14 ,or 17, or the dynamic subframe type selector 1340 described withreference to FIG. 13 or 14 .

At block 2015, the method 2000 may include scheduling a data region ofthe TDD subframe based at least in part on the selected dynamic subframetype. The operation(s) at block 2015 may be performed using the wirelesscommunication manager 1320 described with reference to FIG. 1, 13, 14 ,or 17, or the TDD data region scheduler 1405 described with reference toFIG. 14 .

At block 2020, and in some examples in which the selected dynamicsubframe type is associated with a data region having a UL portion(which UL portion may in some examples include the entire data region),the method 2000 may include scheduling a guard period between a DLcontrol region of the TDD subframe and the data region. The operation(s)at block 2020 may be performed using the wireless communication manager1320 described with reference to FIG. 1, 13, 14 , or 17, or the guardperiod scheduler 1410 described with reference to FIG. 14 .

At block 2025, the method 2000 may include at least one of: allocating aHARQ transmission period for the TDD subframe at an end of the TDDsubframe, allocating at least one HARQ transmission resource for the TDDsubframe in a DL control region of a subsequent subframe, or allocatingat least one DL HARQ transmission resource for the TDD subframe and atleast one UL HARQ transmission resource for the TDD subframe in the TDDsubframe. The operation(s) at block 2025 may be performed using thewireless communication manager 1320 described with reference to FIG. 1,13, 14 , or 17, or the HARQ resource allocator 1415 described withreference to FIG. 14 .

At block 2030, the method 2000 may include transmitting a TDD header ofthe TDD subframe. The TDD header may include the DL control region andan indication of the dynamic subframe type. In some examples, theindication of the dynamic subframe type may be transmitted in the DLcontrol region. In some examples, the DL control region may betransmitted within a temporally first symbol period of the TDD subframe,or within the temporally first symbol period of the TDD subframe and atemporally second symbol period of the TDD subframe. In some examples,the dynamic subframe type may be indicated within the temporally firstsymbol period of the TDD subframe. In some examples, indicating thedynamic subframe type may include at least one of: embedding anindication of the dynamic subframe type in a reference signal,transmitting the indication of the dynamic subframe type in a subframetype indicator channel, or transmitting a type of DCI corresponding tothe dynamic subframe type.

In some examples, indicating the dynamic subframe type may include atleast one of broadcasting the dynamic subframe type to UEs associatedwith a cell, or unicasting the dynamic subframe type to a subset of UEsassociated with the cell. In some examples, indicating the dynamicsubframe type may include transmitting an indication of the dynamicsubframe type within a narrow band of frequencies of a system bandwidth,as described with reference to FIG. 3 . In some examples, indicating thedynamic subframe type may include transmitting at least one of: a firstbit indicating a UL data transmission direction or a DL datatransmission direction, or a second bit indicating a half-duplex datatransmission or a full-duplex data transmission, or a combinationthereof. The operation(s) at block 2030 may be performed using thewireless communication manager 1320 described with reference to FIG. 1,13, 14 , or 17, the TDD header transmission manager 1420 or DL controlregion transmission manager 1425 described with reference to FIG. 14 ,or the dynamic subframe type indication manager 1345 described withreference to FIG. 13 or 14 .

At block 2035, the method 2000 may include transmitting and/or receivingdata in the scheduled data region. The operation(s) at block 2035 may beperformed using the wireless communication manager 1320 described withreference to FIG. 1, 13, 14 , or 17, or the data transmission/receptionmanager 1430 described with reference to FIG. 14 .

At block 2040, the method 2000 may include transmitting and/or receivingat least one HARQ transmission on a HARQ resource scheduled at block2025. The operation(s) at block 2040 may be performed using the wirelesscommunication manager 1320 described with reference to FIG. 1, 13, 14 ,or 17, or the HARQ manager 1435 described with reference to FIG. 14 .

Thus, the method 2000 may provide for wireless communication. It shouldbe noted that the method 2000 is just one implementation and that theoperations of the method 2000 may be rearranged or otherwise modifiedsuch that other implementations are possible.

FIG. 21 is a flow chart illustrating an example of a method 2100 forwireless communication, in accordance with one or more aspects of thepresent disclosure. For clarity, the method 2100 is described below withreference to aspects of one or more of the UEs 115 described withreference to FIG. 1 or 18 , or aspects of the apparatus 1515 describedwith reference to FIG. 15 , or aspects of the wireless communicationmanager 1520 described with reference to FIG. 1, 15, 16 , or 18. In someexamples, a wireless device (e.g., a UE, an apparatus, or a wirelesscommunication manager) may execute one or more sets of codes to controlthe functional elements of the wireless device to perform the functionsdescribed below. Additionally or alternatively, the wireless device mayperform one or more of the functions described below usingspecial-purpose hardware.

At block 2105, the method 2100 may include identifying, in a TDD headerof a subframe, an indication of a dynamic subframe type of the TDDsubframe. In some examples, the dynamic subframe type may include: aDL-centric dynamic subframe type, a UL-centric dynamic subframe type, abi-directional dynamic subframe type, or a full-duplex dynamic subframetype. In some examples, the dynamic subframe type may be identifiedwithin a temporally first symbol period of the TDD subframe. In someexamples, the dynamic subframe type may be identified based at least inpart on at least one of: an indication of the dynamic subframe typeembedded in a reference signal, an indication of the dynamic subframetype received in a subframe type indicator channel, or a type ofreceived DCI. In some examples, the dynamic subframe type may bereceived in at least one of broadcast control information or unicastcontrol information. In some examples, identifying the dynamic subframetype may include identifying an indication of the dynamic subframe typewithin a narrow band of frequencies of a system bandwidth, as describedwith reference to FIG. 3 . In some examples, identifying the dynamicsubframe type may include receiving at least one of: a first bitindicating a UL data transmission direction or a DL data transmissiondirection, or a second bit indicating a half-duplex data transmission ora full-duplex data transmission, or a combination thereof. Theoperation(s) at block 2105 may be performed using the wirelesscommunication manager 1520 described with reference to FIG. 1, 15, 16 ,or 18, or the dynamic subframe type identifier 1535 described withreference to FIG. 15 or 16 .

At block 2110, the method 2100 may include transmitting data orreceiving data in a data region of the TDD subframe based at least inpart on the dynamic subframe type. The operation(s) at block 2110 may beperformed using the wireless communication manager 1520 described withreference to FIG. 1, 15, 16 , or 18, or the data transmission/receptionmanager 1540 described with reference to FIG. 15 or 16 .

Thus, the method 2100 may provide for wireless communication. It shouldbe noted that the method 2100 is just one implementation and that theoperations of the method 2100 may be rearranged or otherwise modifiedsuch that other implementations are possible.

FIG. 22 is a flow chart illustrating an example of a method 2200 forwireless communication, in accordance with one or more aspects of thepresent disclosure. For clarity, the method 2200 is described below withreference to aspects of one or more of the UEs 115 described withreference to FIG. 1 or 18 , or aspects of the apparatus 1515 describedwith reference to FIG. 15 , or aspects of the wireless communicationmanager 1520 described with reference to FIG. 1, 15, 16 , or 18. In someexamples, a wireless device (e.g., a UE, an apparatus, or a wirelesscommunication manager) may execute one or more sets of codes to controlthe functional elements of the wireless device to perform the functionsdescribed below. Additionally or alternatively, the wireless device mayperform one or more of the functions described below usingspecial-purpose hardware.

At block 2205, the method 2200 may include receiving a TDD header of asubframe. The TDD header may include a DL control region and anindication of a dynamic subframe type of the TDD subframe. In someexamples, the indication of the dynamic subframe type may be received inthe DL control region. In some examples, the DL control region may bereceived within a temporally first symbol period of the TDD subframe, orwithin the temporally first symbol period of the TDD subframe and atemporally second symbol period of the TDD subframe. The operation(s) atblock 2205 may be performed using the wireless communication manager1520 described with reference to FIG. 1, 15, 16 , or 18, or the headerprocessor 1605 described with reference to FIG. 16 .

At block 2210, the method 2200 may include identifying, in the TDDheader (and in some examples, in the DL control region), the indicationof the dynamic subframe type. In some examples, the dynamic subframetype may include: a DL-centric dynamic subframe type, a UL-centricdynamic subframe type, a bi-directional dynamic subframe type, afull-duplex dynamic subframe type, a dynamic switch dynamic subframetype, a mixed interference measurement dynamic subframe type, or adistributed scheduling dynamic subframe type. In some examples, thedynamic subframe type may be identified within a temporally first symbolperiod of the TDD subframe. In some examples, the dynamic subframe typemay be identified based at least in part on at least one of: anindication of the dynamic subframe type embedded in a reference signal,an indication of the dynamic subframe type received in a subframe typeindicator channel, or a type of received DCI.

In some examples, the dynamic subframe type may be received in at leastone of broadcast control information or unicast control information. Insome examples, identifying the dynamic subframe type may includeidentifying an indication of the dynamic subframe type within a narrowband of frequencies of a system bandwidth, as described with referenceto FIG. 3 . In some examples, identifying the dynamic subframe type mayinclude receiving at least one of: a first bit indicating a UL datatransmission direction or a DL data transmission direction, or a secondbit indicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof. The operation(s) at block 2210may be performed using the wireless communication manager 1520 describedwith reference to FIG. 1, 15, 16 , or 18, the header processor 1605described with reference to FIG. 16 , or the dynamic subframe typeidentifier 1535 described with reference to FIG. 15 or 16 .

At block 2215, and in some examples in which the identified dynamicsubframe type is associated with a data region having a UL portion(which UL portion may in some examples include the entire data region),the method 2200 may include refraining from transmitting during a guardperiod between the DL control region and the data region. Theoperation(s) at block 2205 may be performed using the wirelesscommunication manager 1520 described with reference to FIG. 1, 15, 16 ,or 18, or the guard period manager 1610 described with reference to FIG.16 .

At block 2220, the method 2200 may include transmitting data orreceiving data in a data region of the TDD subframe based at least inpart on the dynamic subframe type. The operation(s) at block 2220 may beperformed using the wireless communication manager 1520 described withreference to FIG. 1, 15, 16 , or 18, or the data transmission/receptionmanager 1540 described with reference to FIG. 15 or 16 .

At block 2225, the method 2200 may include identifying at least one of:an allocation of a HARQ transmission period for the TDD subframe at anend of the TDD subframe, an allocation of at least one HARQ transmissionresource for the TDD subframe in a DL control region of a subsequentsubframe, or an allocation of at least one DL HARQ transmission resourcefor the TDD subframe and at least one UL HARQ transmission resource forthe TDD subframe in the TDD subframe. The operation(s) at block 2225 maybe performed using the wireless communication manager 1520 describedwith reference to FIG. 1, 15, 16 , or 18, or the HARQ manager 1615described with reference to FIG. 16 .

At block 2230, the method 2200 may include transmitting and/or receivingat least one HARQ transmission on an allocated HARQ resource. Theoperation(s) at block 2230 may be performed using the wirelesscommunication manager 1520 described with reference to FIG. 1, 15, 16 ,or 18, or the HARQ manager 1615 described with reference to FIG. 16 .

Thus, the method 2200 may provide for wireless communication. It shouldbe noted that the method 2200 is just one implementation and that theoperations of the method 2200 may be rearranged or otherwise modifiedsuch that other implementations are possible.

In some examples, aspects from two or more of the methods 1900, 2000,2100 or 2200 described with reference to FIG. 19, 20, 21 or 22 may becombined. It should be noted that the methods 1900, 2000, 2100 and 2200are just example implementations, and that the operations of the methods1900, 2000, 2100 or 2200 may be rearranged or otherwise modified suchthat other implementations are possible.

Techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, single carrierFDMA (SC-FDMA), and other systems. The terms “system” and “network” areoften used interchangeably. A CDMA system may implement a radiotechnology such as CDMA2000, Universal Terrestrial Radio Access (UTRA),etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000Releases 0 and A may be referred to as CDMA2000 1×, 1×, etc. IS-856(TIA-856) may be referred to as CDMA2000 1×EV-DO, High Rate Packet Data(HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants ofCDMA. A TDMA system may implement a radio technology such as GlobalSystem for Mobile Communications (GSM). An OFDMA system may implement aradio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA(E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20,Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal MobileTelecommunication System (UMTS). 3GPP LTE and LTE-A are new releases ofUMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM aredescribed in documents from an organization named 3GPP. CDMA2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). The techniques described herein may beused for the systems and radio technologies mentioned above as well asother systems and radio technologies, including cellular (e.g., LTE)communications over an unlicensed or shared bandwidth. The descriptionabove, however, describes an LTE/LTE-A system for purposes of example,and LTE terminology is used in much of the description above, althoughthe techniques are applicable beyond LTE/LTE-A applications.

The detailed description set forth above in connection with the appendeddrawings describes examples and does not represent all of the examplesthat may be implemented or that are within the scope of the claims. Theterms “example” and “exemplary,” when used in this description, mean“serving as an example, instance, or illustration,” and not “preferred”or “advantageous over other examples.” The detailed description includesspecific details for the purpose of providing an understanding of thedescribed techniques. These techniques, however, may be practicedwithout these specific details. In some instances, well-known structuresand apparatuses are shown in block diagram form in order to avoidobscuring the concepts of the described examples.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), an ASIC, anFPGA or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. A general-purpose processormay be a microprocessor, but in the alternative, the processor may beany conventional processor, controller, microcontroller, or statemachine. A processor may also be implemented as a combination ofcomputing devices, e.g., a combination of a DSP and a microprocessor,multiple microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope and spirit of the disclosure and appended claims. For example,due to the nature of software, functions described above can beimplemented using software executed by a processor, hardware, firmware,hardwiring, or combinations of any of these. Features implementingfunctions may be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations. As used herein, including in the claims,the term “and/or,” when used in a list of two or more items, means thatany one of the listed items can be employed by itself, or anycombination of two or more of the listed items can be employed. Forexample, if a composition is described as containing components A, B,and/or C, the composition can contain A alone; B alone; C alone; A and Bin combination; A and C in combination; B and C in combination; or A, B,and C in combination. Also, as used herein, including in the claims,“or” as used in a list of items (for example, a list of items prefacedby a phrase such as “at least one of” or “one or more of”) indicates aninclusive list such that, for example, a phrase referring to “at leastone of” a list of items refers to any combination of those items,including single members. As an example, “at least one of: A, B, or C”is intended to cover A, B, C, A-B, A-C, B-C, and A-B-C, as well as anycombination with multiples of the same element (e.g., A-A, A-A-A, A-A-B,A-A-C, A-B-B, A-C-C, B-B, B-B-B, B-B-C, C-C, and C-C-C or any otherordering of A, B, and C).

As used herein, the phrase “based on” shall not be construed as areference to a closed set of conditions. For example, an exemplaryoperation that is described as “based on condition A” may be based onboth a condition A and a condition B without departing from the scope ofthe present disclosure. In other words, as used herein, the phrase“based on” shall be construed in the same manner as the phrase “based atleast in part on.”

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media cancomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the scope of thedisclosure. Thus, the disclosure is not to be limited to the examplesand designs described herein but is to be accorded the broadest scopeconsistent with the principles and novel techniques disclosed herein.

What is claimed is:
 1. A method for wireless communication, comprising:selecting a dynamic subframe type of a time division duplex (TDD)subframe based at least in part on a dynamic communication direction ofone or more symbol periods of the TDD subframe, the dynamic subframetype being indicative of the dynamic communication direction of each ofthe one or more symbol periods of the TDD subframe, wherein the dynamicsubframe type comprises at least one uplink data symbol and at least onedownlink data symbol, wherein each of the at least one uplink datasymbol and the at least one downlink data symbol is outside of adownlink control region within the TDD subframe; and indicating, to agroup of user equipment (UEs), the dynamic subframe type in the downlinkcontrol region, wherein the dynamic subframe type is indicated within atemporally first symbol period of the TDD subframe; and wherein theindicating the dynamic subframe type comprises transmitting a type ofdownlink control information (DCI) corresponding to the dynamic subframetype within the temporally first symbol period of the TDD subframe. 2.The method of claim 1, wherein the dynamic subframe type is selectedfrom a set of dynamic subframe types including two or more of: adownlink-centric dynamic subframe type, or an uplink-centric dynamicsubframe type, or a bi-directional dynamic subframe type, or afull-duplex dynamic subframe type, or a dynamic switch dynamic subframetype, or a mixed interference measurement dynamic subframe type, or adistributed scheduling dynamic subframe type.
 3. The method of claim 1,further comprising at least one of: allocating a hybrid automatic repeatrequest (HARQ) transmission period for the TDD subframe at an end of theTDD subframe, or allocating at least one HARQ transmission resource forthe TDD subframe in a downlink control region of a subsequent subframe,or allocating at least one downlink HARQ transmission resource for theTDD subframe and at least one uplink HARQ transmission resource for theTDD subframe in the TDD subframe.
 4. The method of claim 1, furthercomprising: scheduling a data region of the TDD subframe based at leastin part on the selected dynamic subframe type.
 5. The method of claim 4,further comprising: scheduling a guard period between the downlinkcontrol region and the data region when the dynamic subframe type isassociated with the data region having an uplink portion.
 6. The methodof claim 1, wherein indicating the dynamic subframe type comprises:transmitting an indication of the dynamic subframe type within a narrowband of frequencies of a system bandwidth.
 7. The method of claim 1,wherein indicating the dynamic subframe type comprises: transmitting atleast one of: a first bit indicating an uplink data transmissiondirection or a downlink data transmission direction, or a second bitindicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof.
 8. The method of claim 1,further comprising: identifying a traffic condition associated with datato be transmitted between a network access device and at least one UE,the traffic condition comprising an uplink/downlink traffic ratio. 9.The method of claim 8, wherein the dynamic subframe type is selectedbased at least in part on the traffic condition.
 10. The method of claim8, wherein the uplink/downlink traffic ratio comprises a ratio oftraffic queued for transmission to the network access device and trafficqueued for transmission to the at least one UE.
 11. The method of claim1, wherein the dynamic subframe type is an uplink-centric dynamicsubframe type.
 12. The method of claim 1, wherein hybrid automaticrepeat request (HARQ) feedback for transmissions during the TDD subframeis transmitted within the TDD subframe.
 13. The method of claim 1,wherein an allocation of hybrid automatic repeat request (HARQ)resources for the TDD subframe is based at least in part on the dynamicsubframe type.
 14. An apparatus for wireless communication, comprising:means for selecting a dynamic subframe type of a time division duplex(TDD) subframe based at least in part on a dynamic communicationdirection of one or more symbol periods of the TDD subframe, the dynamicsubframe type being indicative of the dynamic communication direction ofeach of the one or more symbol periods of the TDD subframe, wherein thedynamic subframe type comprises at least one uplink data symbol and atleast one downlink data symbol, wherein each of the at least one uplinkdata symbol and the at least one downlink data symbol is outside of adownlink control region within the TDD subframe; and means forindicating, to a group of user equipment (UEs), the dynamic subframetype in the downlink control region, wherein the dynamic subframe typeis indicated within a temporally first symbol period of the TDDsubframe; and wherein the means for indicating the dynamic subframe typecomprises means for transmitting a type of downlink control information(DCI) corresponding to the dynamic subframe type within the temporallyfirst symbol period of the TDD subframe.
 15. The apparatus of claim 14,wherein the dynamic subframe type is selected from a set of dynamicsubframe types including two or more of: a downlink-centric dynamicsubframe type, or an uplink-centric dynamic subframe type, or abi-directional dynamic subframe type, or a full-duplex dynamic subframetype, or a dynamic switch dynamic subframe type, or a mixed interferencemeasurement dynamic subframe type, or a distributed scheduling dynamicsubframe type.
 16. The apparatus of claim 14, further comprising atleast one of: means for allocating a hybrid automatic repeat request(HARQ) transmission period for the TDD subframe at an end of the TDDsubframe, or means for allocating at least one HARQ transmissionresource for the TDD subframe in a downlink control region of asubsequent subframe, or means for allocating at least one downlink HARQtransmission resource for the TDD subframe and at least one uplink HARQtransmission resource for the TDD subframe in the TDD subframe.
 17. Theapparatus of claim 14, further comprising at least one of: means forbroadcasting the dynamic subframe type to UEs associated with a cell.18. The apparatus of claim 14, further comprising: means for schedulinga data region of the TDD subframe based at least in part on the selecteddynamic subframe type.
 19. The apparatus of claim 18, furthercomprising: means for scheduling a guard period between the downlinkcontrol region and the data region when the dynamic subframe type isassociated with the data region having an uplink portion.
 20. Theapparatus of claim 14, wherein the means for indicating the dynamicsubframe type comprises: means for transmitting an indication of thedynamic subframe type within a narrow band of frequencies of a systembandwidth.
 21. The apparatus of claim 14, wherein the means forindicating the dynamic subframe type comprises: means for transmittingat least one of: a first bit indicating an uplink data transmissiondirection or a downlink data transmission direction, or a second bitindicating a half-duplex data transmission or a full-duplex datatransmission, or a combination thereof.
 22. The apparatus of claim 14,further comprising: means for identifying a traffic condition associatedwith data to be transmitted between a network access device and at leastone UE, the traffic condition comprising an uplink/downlink trafficratio.
 23. The apparatus of claim 22, wherein the dynamic subframe typeis selected based at least in part on the traffic condition.
 24. Theapparatus of claim 22, wherein the uplink/downlink traffic ratiocomprises a ratio of traffic queued for transmission to the networkaccess device and traffic queued for transmission to the at least oneUE.
 25. The apparatus of claim 14, wherein the dynamic subframe type isan uplink-centric dynamic subframe type.
 26. The apparatus of claim 14,comprising means for transmitting hybrid automatic repeat request (HARQ)feedback for transmissions during the TDD subframe within the TDDsubframe.
 27. The apparatus of claim 14, wherein an allocation of hybridautomatic repeat request (HARQ) resources for the TDD subframe is basedat least in part on the dynamic subframe type.
 28. An apparatus forwireless communication, comprising: a processor; and memory coupled withthe processor; the processor and the memory configured to: select adynamic subframe type of a time division duplex (TDD) subframe based atleast in part on a dynamic communication direction of one or more symbolperiods of the TDD subframe, the dynamic subframe type being indicativeof the dynamic communication direction of each of the one or more symbolperiods of the TDD subframe, wherein the dynamic subframe type comprisesat least one uplink data symbol and at least one downlink data symbol,wherein each of the at least one uplink data symbol and the at least onedownlink data symbol is outside of a downlink control region within theTDD subframe; indicate, to a group of user equipment (UEs), the dynamicsubframe type in a temporally first symbol period of the TDD subframe;and transmit a type of downlink control information (DCI) correspondingto the dynamic subframe type within the temporally first symbol periodof the TDD subframe.
 29. The apparatus of claim 28, wherein the dynamicsubframe type is selected from a set of dynamic subframe types includingtwo or more of: a downlink-centric dynamic subframe type, or anuplink-centric dynamic subframe type, or a bi-directional dynamicsubframe type, or a full-duplex dynamic subframe type, or a dynamicswitch dynamic subframe type, or a mixed interference measurementdynamic subframe type, or a distributed scheduling dynamic subframetype.
 30. The apparatus of claim 28, wherein the processor and thememory are further configured to: allocate a hybrid automatic repeatrequest (HARQ) transmission period for the TDD subframe at an end of theTDD subframe, or allocate at least one HARQ transmission resource forthe TDD subframe in a downlink control region of a subsequent subframe,or allocate at least one downlink HARQ transmission resource for the TDDsubframe and at least one uplink HARQ transmission resource for the TDDsubframe in the TDD subframe.
 31. The apparatus of claim 28, wherein theprocessor and the memory are further configured to: schedule a dataregion of the TDD subframe based at least in part on the selecteddynamic subframe type.
 32. The apparatus of claim 31, wherein theprocessor and the memory are further configured to: schedule a guardperiod between the downlink control region of the TDD subframe and thedata region when the dynamic subframe type is associated with the dataregion having an uplink portion.
 33. The apparatus of claim 28, whereinindicating the dynamic subframe type comprises the processor and thememory further configured to: transmit an indication of the dynamicsubframe type within a narrow band of frequencies in a system bandwidth.34. The apparatus of claim 28, wherein indicating the dynamic subframetype comprises the processor and the memory further configured to:transmit at least one of: a first bit indicating an uplink datatransmission direction or a downlink data transmission direction, or asecond bit indicating a half-duplex data transmission or a full-duplexdata transmission, or a combination thereof.
 35. The apparatus of claim28, wherein the processor and the memory are further configured to:identify a traffic condition associated with data to be transmittedbetween a network access device and at least one UE, the trafficcondition comprising an uplink/downlink traffic ratio.
 36. The apparatusof claim 35, wherein the dynamic subframe type is selected based atleast in part on the traffic condition.
 37. The apparatus of claim 35,wherein the uplink/downlink traffic ratio comprises a ratio of trafficqueued for transmission to the network access device and traffic queuedfor transmission to the at least one UE.
 38. The apparatus of claim 28,wherein the dynamic subframe type is an uplink-centric dynamic subframetype.
 39. The apparatus of claim 28, wherein the processor and thememory are configured to transmit hybrid automatic repeat request (HARQ)feedback for transmissions during the TDD subframe within the TDDsubframe.
 40. The apparatus of claim 28, wherein an allocation of hybridautomatic repeat request (HARQ) resources for the TDD subframe is basedat least in part on the dynamic subframe type.
 41. A non-transitorycomputer-readable medium storing code for wireless communication, thecode comprising instructions executable by a processor to: select adynamic subframe type of a time division duplex (TDD) subframe based atleast in part on a dynamic communication direction of one or more symbolperiods of the TDD subframe, the dynamic subframe type being indicativeof the dynamic communication direction of each of the one or more symbolperiods of the TDD subframe, wherein the dynamic subframe type comprisesat least one uplink data symbol and at least one downlink data symbol,wherein each of the at least one uplink data symbol and the at least onedownlink data symbol is outside of a downlink control region within theTDD subframe; and indicate, to a group of user equipment (UEs), thedynamic subframe type in a temporally first symbol period of thedownlink control region by transmitting a type of downlink controlinformation (DCI) corresponding to the dynamic subframe type within thetemporally first symbol period of the TDD subframe.
 42. Thenon-transitory computer-readable medium of claim 41, wherein the dynamicsubframe type is selected from a set of dynamic subframe types includingtwo or more of: a downlink-centric dynamic subframe type, or anuplink-centric dynamic subframe type, or a bi-directional dynamicsubframe type, or a full-duplex dynamic subframe type, or a dynamicswitch dynamic subframe type, or a mixed interference measurementdynamic subframe type, or a distributed scheduling dynamic subframetype.
 43. The non-transitory computer-readable medium of claim 41,wherein the dynamic subframe type is an uplink-centric dynamic subframetype.
 44. The non-transitory computer-readable medium of claim 41, thecode comprising instructions to transmit hybrid automatic repeat request(HARQ) feedback for transmissions during the TDD subframe within the TDDsubframe.
 45. The non-transitory computer-readable medium of claim 41,wherein an allocation of hybrid automatic repeat request (HARQ)resources for the TDD subframe is based at least in part on the dynamicsubframe type.